WO2019174582A1 - Message transmission method and device - Google Patents

Abstract

A message transmission method and device. The method comprises: a first network element receiving a first request from a sending end, said first request comprising configuration parameters and being used to request configuration of a terminal device according to the configuration parameters, and said first network element belonging to a first network; and after receiving the first request from the sending end, the first network element sending the first request to the terminal device by means of an NAS message. In vertical industry application of mobile networks, terminal devices belonging to different vertical industries can all be configured by means of the described method, without the need to deploy dedicated servers or establish dedicated channels for terminal devices belonging to different vertical industries, thus lowering the cost and complexity of deployment.

Description

Message transmission method and device

The present application claims priority to Chinese Patent Application No. 201101206475.4, entitled "A Message Transmission Method and Apparatus", filed on March 13, 2018, the entire disclosure of which is incorporated herein by reference. .

Technical field

The present application relates to the field of mobile communications technologies, and in particular, to a message transmission method and apparatus.

Background technique

The Multefire Alliance proposes a Multefire technology, which refers to the technology of building a new wireless network by independently running long term evolution (LTE) technology on unlicensed spectrum (such as the global 5GHz unlicensed spectrum). The wireless network built using the Multefire technology is called a neutral host network (NHN).

In the prior art, the terminal device is allowed to directly access the 3rd Generation Partnership Project (3GPP) core network or a participating service provider (PSP) network from the access network element in the NHN network. The terminal device is allowed to access the 3GPP core network or the PSP network from the access network element in the NHN network via the core network of the NHN network. For convenience of description, the core network of the NHN network is simply referred to as the NHN core network.

In the scenario where the terminal device accesses the 3GPP core network or the PSP network via the NHN core network, the third-party server usually configures the terminal device by using a specially configured configuration server, and the configuration process depends on the special establishment established between the terminal device and the configuration server. Channels, when mobile networks are used in vertical industries, different configurations may be required for terminal equipment belonging to different vertical industries. If the prior art method is used, different configuration servers need to be deployed separately for different vertical industries, and different The configuration server needs to establish a dedicated channel with the corresponding terminal device, which causes high cost and complicated deployment.

Summary of the invention

The embodiment of the present application provides a message transmission method and apparatus, which are used to implement configuration of a terminal device without adding a dedicated configuration server.

To achieve the above objective, the embodiment of the present application provides the following technical solutions:

The first aspect provides a message transmission method, including: receiving, by a first network element, a first request from a sending end, where the first request includes a configuration parameter, where the first request is used to request to configure the terminal device according to the configuration parameter, where the first network The element belongs to the first network, and after receiving the first request from the sending end, the first network element sends a first request to the terminal device through a non-access stratum (NAS) message. When the mobile network is applied to the vertical industry, the terminal devices belonging to different vertical industries can be configured by the above methods, and it is not necessary to deploy a dedicated configuration server and establish a dedicated channel for terminal devices belonging to different vertical industries, thereby reducing the deployment cost and Deployment complexity.

Optionally, the configuration parameter may include at least one configuration type, where the configuration type may include configuration and configuration update, software firmware management, status and performance monitoring, and diagnosis, and each configuration type includes different configuration content. For example, the configuration content included in the software firmware management may be a version of the terminal device, a software module loading, a software module update, and a software module uninstallation. The configuration content included in the status and performance monitoring may be monitoring the status and performance of the terminal device, and the diagnosis. The configuration content included may be to diagnose the connection and service problems of the terminal device and to guide the terminal device to perform the next operation.

In a possible design, after the first network element sends the first request to the terminal device through the NAS message, the first network element may also receive the first response from the terminal device for the first request.

After receiving the first response sent by the terminal device, the first network element may send the first response to the sending end, so that the sending end performs subsequent processing according to the first response of the terminal device. In a possible design, the first network element sends a first response to the sending end by using the third network element and the fourth network element, where the third network element belongs to the first network, and the fourth network element belongs to the second network. In another possible design, the first network element sends a first response to the sending end by using the second network element, where the second network element belongs to the first network or belongs to the second network.

In a possible design, the first response includes one or more of the following information: the confirmation information of the first request by the terminal device, the identification information of the terminal device, the identification information of the fourth network element, and the fourth network. The reference identification information of the element and the status information of the terminal device.

In a possible design, before the first network element sends the first request to the terminal device, receiving an authorization indication from the third network element, where the authorization indication is used to indicate that the first network supports the configuration requested by the first request, by using the The method, the first network element does not send a configuration request that is not supported by the first network to the terminal device, which can save signaling overhead.

In this application, the first request for receiving the first request from the sender is not limited. In a possible design, the first network element receives the first request from the transmitting end through the second network element, and the second network element belongs to the first network or belongs to the second network. When the first network element receives the first request from the sending end by using the second network element, the second network element first receives the first request from the sending end, and determines, according to the identification information of the terminal device included in the first request, that the terminal device is in the first In a network, the first request is sent to the first network element.

In a possible design, when the second network element belongs to the first network, the first request sent by the second network element to the first network element may further include a third indication, where the third indication is used to indicate the first request. From the first network.

In a possible design, before the second network element sends the first request to the first network element, it may also determine that the first network supports the configuration requested by the first request. In the case that the configuration parameter includes at least one configuration type, the configuration type includes configuration and configuration update, software firmware management, status and performance monitoring, and diagnosis, and each configuration type includes different configuration contents, the second network element determines the first network. Supporting the configuration requested by the first request, specifically, the second network element determines that the first network supports at least one configuration type, and supports different configuration contents included in each configuration type.

In this application, before receiving the first request from the sending end, the terminal device may further determine that the terminal device supports configuring the terminal device by using the NAS message. In a possible design, the second network element determines that the terminal device supports configuration of the terminal device through the NAS message.

In another possible design, the first network element determines that the terminal device supports configuration of the terminal device through the NAS message. With the method, the first network element or the second network element sends the first request to the terminal device after determining that the terminal device supports the configuration by using the NAS message, because the terminal device does not support the NAS message through the NAS device. Sending the first request to the terminal device in the case of configuration may result in a transmission failure or an error, so that the terminal device may be prevented from failing or receiving an error when receiving the first request.

In a possible design, the first network element may determine that the terminal device supports configuring the terminal device by using a NAS message by: receiving, by the first network element, a first indication from the terminal device, where the first indication is used to indicate the terminal device The terminal device is configured to be configured by using the NAS message, and the first network element determines, according to the first indication, that the terminal device supports configuring the terminal device by using the NAS message.

In a possible design, the first network element determines that the terminal device supports the configuration of the terminal device by using the NAS message, and may send a second indication to the terminal device, where the second indication is used to indicate that the first network supports configuring the terminal by using the NAS message. The device is such that the terminal device preferentially accesses the first network.

In a possible design, the first network element receives the first indication from the terminal device and sends a second indication to the terminal device in a process of network discovery before the terminal device accesses the first network. In another possible design, the first network element receives the first indication from the terminal device during the authentication process with the terminal device, and sends the second indication to the terminal device. In another possible design, the first network element receives the first indication from the terminal device during the registration process with the terminal device, and sends a second indication to the terminal device.

In one possible design, the first network is an NHN network and the second network is a 3GPP network or a PSP network.

In a second aspect, a message transmission apparatus is provided, which has the function of implementing the first network element in the foregoing method embodiment. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the apparatus includes: a processor, a transceiver, a memory; the memory is for storing a computer to execute instructions, the transceiver is configured to implement the device to communicate with other communication entities, and the processor and the memory pass A bus connection, the processor executing the computer-executable instructions stored by the memory to cause the message transmission device to perform the method of the first aspect described above when the device is in operation.

In a third aspect, a message transmission apparatus is provided, the apparatus having the function of implementing the second network element in the foregoing method embodiment. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the apparatus includes: a processor, a transceiver, a memory; the memory is for storing a computer to execute instructions, the transceiver is configured to implement the device to communicate with other communication entities, and the processor and the memory pass A bus connection, the processor executing the computer-executable instructions stored by the memory to cause the message transmission device to perform the method of the first aspect described above when the device is in operation.

In a fourth aspect, a message transmission apparatus is provided, the apparatus having the function of implementing the terminal device in the foregoing method embodiment. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the apparatus includes: a processor, a transceiver, a memory; the memory is for storing a computer to execute instructions, the transceiver is configured to implement the device to communicate with other communication entities, and the processor and the memory pass A bus connection, the processor executing the computer-executable instructions stored by the memory to cause the message transmission device to perform the method of the first aspect described above when the device is in operation.

In a fifth aspect, an embodiment of the present application provides a computer storage medium, configured to store computer software instructions for use by a first network element, where the program includes a program designed to perform the foregoing aspects for the first network element.

In a sixth aspect, an embodiment of the present application provides a computer storage medium for storing computer software instructions for use by a second network element, where the program is configured to execute the foregoing aspect for the second network element.

In a seventh aspect, the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the terminal device, which includes a program designed to execute the foregoing aspects for the terminal device.

In an eighth aspect, an embodiment of the present application provides a computer program product. The computer program product includes computer software instructions that are loadable by a processor to implement the processes of the first aspect method described above.

In a ninth aspect, the embodiment of the present application provides a chip, including a processor, a transceiver component, and optionally, a memory, for performing the message transmission method of the foregoing aspect.

DRAWINGS

1 is a schematic diagram of a network architecture involved in an embodiment of the present application;

2 is a schematic diagram of a network architecture involved in an embodiment of the present application;

3 is a schematic diagram of a network architecture involved in an embodiment of the present application;

FIG. 4 is a schematic diagram of a message transmission method according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a method for negotiating a terminal device by using a NAS message according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of another method for negotiating a terminal device by using a NAS message according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of another method for negotiating a terminal device by using a NAS message according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of still another method for transmitting a message according to an embodiment of the present application;

FIG. 9 is a schematic diagram of still another method for transmitting a message according to an embodiment of the present application;

FIG. 10 is a schematic diagram of still another method for transmitting a message according to an embodiment of the present application;

FIG. 11 is a schematic diagram of still another method for transmitting a message according to an embodiment of the present application;

FIG. 12 is a schematic diagram of still another method for transmitting a message according to an embodiment of the present application;

FIG. 13 is a schematic diagram of still another method for transmitting a message according to an embodiment of the present application;

FIG. 14 is a message transmission apparatus according to an embodiment of the present application;

FIG. 15 is another message transmission apparatus according to an embodiment of the present application.

detailed description

The present application will be specifically described below in conjunction with the drawings.

The terminal device in the present application is a device with wireless transceiving function, which can be deployed on land, including indoor or outdoor, handheld or on-board; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air ( Such as airplanes, balloons and satellites, etc.). The terminal device may be a user equipment (UE) or a customer premise equipment (CPE). For example, it may be a mobile phone, a tablet, a computer with wireless transceiver function, and a virtual device. Virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self driving, remote medical A wireless terminal, a wireless terminal in a smart grid, a wireless terminal in a transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, and the like.

1-3 is a schematic diagram of a network architecture applied to an embodiment of the present application. The scenario shown in FIG. 1 to FIG. 3 is a scenario in which the terminal device accesses the 3GPP core network or the PSP network from the access network element in the NHN network via the core network of the NHN network. The 3GPP core network involved in FIG. 1 is a 4G network, and the 3GPP core network involved in FIG. 2 to FIG. 3 is a 5G network. In the network architecture shown in FIG. 1, the terminal device can also access the access network from the NHN network. The local authentication authorization accounting proxy (Local AAA Proxy) network element is connected to the PSP network through the service provider authentication and authentication (PSP AAA) network element. In Figure 1-3, the terminal device is used as the UE as an example.

For the network architecture shown in FIG. 1 , the network architecture diagram includes a UE, an access network element, an evolved packet data gateway (ePDG), a packet data network gateway (PDN gateway, PGW), 3rd generation partnership project authentication authorization (3GPP AAA), home subscriber server (HSS), service capability exposure function (SCEF), neutral deployment mobile Neutral host mobile management entity (NH MME), neutral host gateway (NH GW), interworking service capability exposure function (IWK-SCEF), Local AAA Proxy, PSP AAA, etc. .

In the network architecture shown in Figure 1, the NHN network can communicate with the 4G network through two modes. In an interworking mode, the NHN network is connected to the 4G network through the ePDG, and the interfaces include SWa-N, SWn, S2b, and SWm. . In another interworking mode, the NH GW network element of the NHN network is connected to the PGW network element of the 4G network through the S2a-N interface, and the used interface includes STa-N. In addition, the Local AAA Proxy network element of the NHN network can also be connected to the PSP AAA network element of the PSP network through the AAA interface.

The function of the network element involved in the network architecture shown in FIG. 1 is briefly introduced below.

The access network element refers to an access network element in the NHN network, and is used for the UE to access the NHN network. For example, it may be a base station.

The ePDG is used to establish an internet protocol security (IPsec) tunnel with the UE when the UE accesses through the non-3GPP (Non-3GPP or N3GPP) access network.

The main functions of the PGW include user-based packet filtering, lawful interception, inter-network protocol (IP) address allocation between UEs, packet transmission level marking in the uplink, and uplink and downlink. Service class level charging and control of service level thresholds, control of service-based uplink and downlink rates, and the like.

3GPP AAA is used to provide functions such as authentication and authorization message brokers.

The HSS is used to store user subscription information, and is responsible for storing information related to the user, such as user identification, number and routing information, security information, location information, profile information, and the like.

The SCEF is an open capability platform in the 4G network. The third party can invoke an application programming interface (API) provided by the operator to subscribe to the 3GPP system through the SCEF.

The NH MME is similar to the MME in the 4G network. Its main function is to support NAS signaling and NAS signaling encryption, PGW selection, assigning temporary identity to the UE, and providing roaming, tracking, security and other functions.

The NH GW is similar to the PGW and the serving gateway (SGW) in the 4G network. The main functions include the user-based packet filtering function, the lawful interception function, the IP address allocation function between the UE's networks, and the uplink. The packet transmission level flag, the uplink and downlink service level charging and the service level threshold control, the service-based uplink and downlink rate control, and the like.

The Local AAA Proxy is used to provide functions such as authentication and authorization message brokers.

The IWK-SCEF is an open capability platform in the NHN network. When interworking with the 3GPP network, the event report of the subscription can be directly reported to the SCEF in the 3GPP network.

PSP AAA is used to provide functions such as authentication and authorization message brokers.

It should be understood that the foregoing NH MME, NH GW, IWK-SCEF, and Local AAA Proxy network elements are network elements belonging to the NHN network. The HSS, SCEF, ePDG, PGW, and 3GPP AAA network elements are network elements belonging to the 3GPP network. The PSP AAA network element is a network element that belongs to the PSP network. The PSP network may also include a SCEF network element (not shown in FIG. 1). The SCEF in the PSP network is similar to the SCEF function in the 3GPP network, and is not described here.

It should be understood that, in some scenarios, the NH MME in the NHN network may be combined with the PSP AAA network element in one device, and the IWK-SCEF network element in the NHN network may be combined with the SCEF network element in the PSP network. In one device, of course, the NH MME, IWK-SCEF, and Local AAA proxy network elements in the NHN network can also be combined with the PSP AAA and SCEF network elements in the PSP network in one device. In these scenarios, the NHN network and A PSP network can be understood as the same network.

The network elements related to the present application mainly include: UE, NH MME, SCEF, IWK-SCEF, and HSS.

For the network architecture shown in FIG. 2 to FIG. 3, the network architecture diagram includes a UE, an access network element, an access and mobility management function (AMF), and a session management function (session management function, SMF), policy control function (PCF), unified data management (UDM), user plane function (UPF), authentication server function (AUSF), network open Network exposure function (NEF), neutral host access and mobility management function (NH AMF), neutral host session management function (NH SMF), neutral deployment user Neutral host user plane function (NH UPF), interworking network exposure function (IWK-NEF), data network (DN), etc. The difference between the network architecture shown in FIG. 2 and FIG. 3 is that the NHN network and the 5G network in FIG. 3 are interworking through a non-3GPP Interworking Function (N3IWF) network element, and the N3IWF network element is similar to the 4G network. The ePDG is used to establish an IPsec tunnel with the UE when the UE accesses through the N3GPP access network. In the future 5G definition, the name of the N3IWF may be changed. This application only exemplifies the non-3GPP network access gateway as the N3IWF.

It should be understood that the NHN network is constantly evolving, and the next-generation NHN network architecture and the interworking architecture of NHN and 5G networks are still under study. In the future 5G definition, the network architecture and network shown in Figure 2-3 The names of the network elements involved in the architecture may be changed. This application is only illustrated by the network architecture shown in Figure 2 and Figure 3 and the network elements involved in the network architecture.

The functions of the network elements involved in the network architecture shown in FIG. 2 to FIG. 3 are briefly introduced below.

The access network element refers to an access network element in the NHN network, and is used for the UE to access the NHN network. For example, it may be a base station.

The AMF is responsible for access management and mobility management of the terminal equipment. In practical applications, it includes the mobility management function of the MME in the 4G network and adds the access management function.

The SMF is responsible for session management, such as user session establishment.

The UPF is a functional network element of the user plane. It is mainly responsible for connecting to the external network. It includes the functions of the SGW and the PGW of the 4G network, and is mainly responsible for packet data packet forwarding and accounting information statistics.

The UDM is used to manage the user's subscription information, and implements a backend similar to the HSS in 4G.

The NEF is an open capability platform in the 5G network. When interworking with the NHN network, the NEF can directly report the event report of the subscription to the IWK-NEF in the NHN network.

NH AMF is similar to AMF in 5G networks and is responsible for access management and mobility management of terminal devices.

The NH SMF is similar to the SMF in a 5G network and is responsible for session management, such as user session establishment.

The NH UPF is similar to the UPF in the 5G network, and is mainly responsible for connecting external networks, forwarding of packet data packets, and accounting information statistics.

The IWK-NEF is an open capability platform in the NHN network. When interworking with the 5G network, the event can be directly reported to the NEF in the 5G network.

The DN is responsible for providing services for the terminal devices. For example, some DNs provide Internet access for terminal devices, and other DNs provide SMS functions for terminal devices.

The network elements related to the present application mainly include: UE, NH AMF, AMF, UDM, PCF, IWK-NEF, NEF, and N3IWF.

For the network architecture shown in FIG. 1 to FIG. 3, in the prior art, if the sending end requests to configure the UE, the configuration server needs to be configured according to the specially deployed configuration server, and the configuration process depends on the UE and the configuration server. Established a dedicated channel. Specifically, the sending end sends a configuration request to the configuration server through the application layer message, and then the configuration server forwards the configuration request to the UE. In the process, the configuration server transparently forwards the configuration request sent by the sending end, that is, the configuration server receives the configuration request. The configuration request does not do anything. When the networks shown in FIG. 1 to FIG. 3 are applied to the vertical industry, UEs belonging to different vertical industries may need to be configured differently. If the UEs belonging to different vertical industries are configured by the above method, they are different. The UEs in the vertical industry need to deploy different configuration servers separately, and different configuration servers need to establish dedicated channels respectively with the corresponding UEs, which may result in high deployment cost and complicated deployment. In addition, in the prior art, the method in which the sending end sends a configuration request to the UE through the application layer message also needs the UE to support the ip protocol series. That is, the method can only be used for the UE supporting the ip protocol stack. This method is not applicable to UEs that support the ip protocol stack.

The embodiment of the present application provides a message transmission method and apparatus for the above problem, which is used to configure a terminal device through an NHN network without adding a dedicated configuration server, and can be configured by the method provided by the present application. Terminal devices that support the ip protocol stack can also be configured with terminal devices that do not support the ip protocol stack. The method is applicable to the interworking architecture of the NHN network and the 4G network shown in FIG. 1 , and also to the interworking architecture of the NHN network and the 5G network shown in FIG. 2 to FIG. 3 .

In the present application, for convenience of description, the NHN network is referred to as a first network. Of course, the present application does not limit the first network, for example, other non-3GPP networks, and the following uses the first network as the NHN network. Example description.

The second network in this application is a network that can enable both the transmitting end and the first network to communicate with each other. For example, it can be a 3GPP network.

The sender in the present application is a device that can request configuration of the terminal device, and may be, for example, a server (such as a third-party server), where the third-party server refers to a server that does not belong to the first network.

The message transmission method of the present application will be described below with reference to the accompanying drawings.

Referring to FIG. 4, a flow chart of a message transmission method provided by the present application includes the following steps:

S101: The first network element receives the first request from the sending end.

In this application, the first request may include a configuration parameter, and when the first request includes the configuration parameter, the first request is used to request to configure the terminal device according to the configuration parameter. The first network element belongs to the first network. When the first network is an NHN network, the first network element may be an NH MME or an NH AMF.

Optionally, the configuration parameter may include at least one configuration type, where the configuration type may include configuration and configuration update, software firmware management, status and performance monitoring, and diagnosis, and each configuration type includes different configuration content. For example, the configuration content included in the software firmware management may be a version of the terminal device, a software module loading, a software module update, and a software module uninstallation. The configuration content included in the status and performance monitoring may be monitoring the status and performance of the terminal device, and the diagnosis. The configuration content included may be to diagnose the connection and service problems of the terminal device and to guide the terminal device to perform the next operation.

In this application, the first request for receiving the first request from the sender is not limited. In a possible implementation manner, referring to S101a-S101b, the first network element receives the first request from the sending end by using the second network element, and specifically, the second network element receives the first request from the sending end, according to the first request. The identifier information of the terminal device is included, determining that the terminal device is in the first network, and sending the first request to the first network element.

In a possible implementation manner, the second network element receives the first request from the sending end by using the fourth network element. In the implementation manner, after receiving the first request from the sending end, the fourth network element determines whether the sending end can If the terminal device is configured to be configured, the fourth network element sends a first request to the second network element, and if it is determined that the sending end cannot configure the terminal device, the fourth network element is configured. Send a failure message to the sender. In the present application, the transmitting end can configure the terminal device as an example, and refer to S101a1-S101a3.

Optionally, the second network element belongs to the first network or belongs to the second network. When the second network element belongs to the first network, that is, belongs to the NHN network, the second network element may be a device composed of a local AAA proxy, a PSP AAA, an IWK-SCEF, and a SCEF network element. In the case of the second network element, for example, when the second network element belongs to the 3GPP network, the second network element may be a network element such as an HSS, a UDM, a PCF, or an SCEF, and for example, when the second network element belongs to the PSP network, the second network element It can be a network element such as PSP AAA and SCEF.

Optionally, when the second network element belongs to the first network, when the second network element sends the first request to the first network element, the third network element may carry a third indication, where the third indication is used to indicate that the first request is from the first network.

It should be understood that, in the present application, the first request from the first network element to receive the first request from the sending end through the second network element is not limited. In a possible implementation manner, the first network element directly receives the first request from the second network element, and in another possible implementation manner, the first network element receives the first from the second network element by using another network element. request. For example, the first network element is an NH AMF network element, and the second network element is a UDM network element. The other network element may be an AMF network element. For example, the first network element is the NH MME and the second network element is the HSS network element. The other network element may be a network element such as 3GPP AAA or Local AAA Proxy. The following describes in detail how the first network element receives the first request from the sending end by using the second network element, and details are not described herein.

In this application, the identifier information of the terminal device refers to information that can uniquely identify the terminal device, for example, may be the ID of the terminal device.

Optionally, after receiving the first request from the sending end, the first network element may further send a response message for the first request to the sending end, refer to S101′, S101a′, and S101b′. The response message may include confirmation information of the first request by the first network element, for example, may be a message confirming receipt of the first request, or a message confirming that the first request is not received. In the present application, the case where the first network element confirms receipt of the first request is taken as an example for description. If the first network element does not receive the first request, the first request may be further requested to be resent.

It should be understood that, in this application, the first network element sends a response message to the first request to the sending end, and may send the same message by receiving the same request from the sending end, and details are not described herein again.

S102: The first network element sends the first request to the terminal device by using the NAS message.

In this application, the first request is sent to the terminal device by using the first network element in the NHN network. Specifically, the first network element sends the first request to the terminal device by using the NAS message, and the application does not need to add a special network to the existing network. The configuration server does not send the first request to the terminal device through the application layer message, but sends the first request to the terminal device through the NAS message.

Optionally, the NAS message may be a new NAS message, or may be a NAS message obtained by modifying an existing NAS message. When the NAS message is a NAS message obtained by modifying an existing NAS message, an indication may be added to the existing NAS message to indicate that the modified NAS message carries the first request.

Optionally, if the NAS message is a NAS message obtained by modifying an existing NAS message, the first network element may separately send the NAS message to the terminal device, or may also send the NAS message to the terminal device at the time. The message carries the NAS message.

It should be understood that, if the first network element receives the first request from the sending end by using the second network element and other network elements, the first request may be performed when the second network element and the other network element forward the first request from the sending end. Further parsing and encapsulation processing, that is, the second network element and other network elements send different messages carrying the first request, and specific parameters in the first request sent by different network elements may also be different.

In this application, the first request is sent to the terminal device by using the first network element in the first network. When the mobile network is applied to the vertical industry, the terminal devices belonging to different vertical industries can be configured by using the method of the present application, that is, Sending configuration-related information (for example, configuration request, configuration parameters, and the like) to the terminal device through the first network element in the first network, without deploying a dedicated configuration server and establishing a dedicated channel for terminal devices belonging to different vertical industries. Therefore, the deployment cost and deployment complexity can be reduced by the method of the present application. In addition, in the present application, the first network element sends the first request to the terminal device by using the NAS message instead of the application layer message, so the method is applicable to both the terminal device supporting the ip protocol stack and the terminal device not supporting the ip protocol stack. The method provided by the present application is not limited in the types of terminal devices that can be configured.

S103: The terminal device sends a first response to the first request to the first network element by using the NAS message.

Optionally, the first response includes one or more of the following information: the confirmation information of the first request by the terminal device, the identifier information of the terminal device, the identifier information of the fourth network element, and the reference identifier of the fourth network element. Information and status information of the terminal device.

In the present application, the confirmation information of the first request by the terminal device refers to the message confirming receipt of the first request. Of course, in other implementation manners, the confirmation information may also be a message confirming that the first request is not received. In this case, the terminal device may further request to resend the first request or the like.

In the present application, the fourth network element belongs to the second network. For example, for the network architecture shown in FIG. 1, the fourth network element may be a SCEF. For the network architecture shown in FIG. 2 to FIG. 3, the fourth network element may be NEF network element.

In this application, the identifier information of the fourth network element is information that can uniquely identify the fourth network element, for example, may be the ID of the fourth network element.

In this application, the reference identifier information of the fourth network element refers to the reference identifier information that can uniquely identify the configuration request in the fourth network element, for example, may be the reference ID of the fourth network element.

In a possible implementation manner, for the first request sent by the sending end, the terminal device needs to send its own state, state change, or statistical data for a period of time to the transmitting end. In this scenario, the terminal device sends The first response may include identification information of the terminal device, status information of the terminal device, and the like.

In this application, if the terminal device needs to send the status information of the terminal device to the sending end, the first network element needs to forward the first response to the sending end after receiving the first response sent by the terminal device. The application does not limit how the first network element sends the first response to the sending end. In a possible implementation manner, the first network element sends the first response to the sending end by using the second network element, and refer to S104a-S104b. In another possible implementation manner, the first network element passes the third network element and the first network element. The four network elements send a first response to the sender, see S105a-S105c. If the third network element and the fourth network element send the first response to the sending end, the fourth network element may send the first response to the sending end according to the reference ID of the fourth network element.

The third network element belongs to the first network, and the fourth network element belongs to the second network. For example, for the network architecture shown in FIG. 1, the third network element may be IWK-SCEF, and the fourth network element may be SCEF. For the network architecture shown in FIG. 2 to FIG. 3, the third network element may be IWK-NEF. The fourth network element may be NEF.

It should be understood that, if the first network element sends the first response to the sending end by using the second network element or the third network element and the fourth network element, the first network element forwards from the second network element, the third network element, and the fourth network element. The first response of the terminal device may further parse and encapsulate the first response, that is, the second network element, the third network element, and the fourth network element send different messages carrying the first response, and different network elements send The specific parameters in the first response may also vary.

It should be understood that, because the fourth network element belongs to the second network, the identifier information of the fourth network element and/or the reference identification information of the fourth network element may be included in the first response, so that the first network element can find the fourth network element. Network element.

S104a: The first network element sends a first response to the second network element.

S104b: The second network element sends a first response to the sending end.

S105a: The first network element sends a first response to the third network element.

S105b: The third network element sends a first response to the fourth network element.

S105c: The fourth network element sends a first response to the sending end.

It should be understood that the first network element may select whether to use the S104a-S104b mode or the S105a-S105c to send the first response to the transmitting end according to actual requirements.

In this application, if the first network element receives the first request from the sending end by using the second network element, before the second network element sends the first request to the first network element, it may also determine whether the first network supports the first requesting station. The configuration of the request, if it is determined that the first network supports the configuration requested by the first request, sending a first request to the first network element, and if it is determined that the first network does not support the configuration requested by the first request, sending the failure to the sending end Message. In the present application, the case where the first network supports the configuration requested by the first request is taken as an example, and reference is made to S101c.

In a possible implementation manner, the configuration requested by the first network to support the first request refers to the configuration type included in the first network support configuration parameter, and the different configuration content included in each configuration type is supported. For example, if the configuration type requested by the sender is a configuration and a configuration update, and the configuration content included in the configuration type is a request to configure a new service, the configuration requested by the first network to support the first request refers to whether the first network supports the The configuration of the new service.

In this application, before the first network element sends the first request to the terminal device, the first network may also determine the configuration requested by the first network to support the first request, for example, the first network support may be determined by receiving an authorization indication from the third network element. A request for the requested configuration. The authorization indication is used to indicate that the first network supports the configuration requested by the first request. For example, the configuration requested by the first network to support the first request refers to the configuration type included in the first network support configuration parameter, and the different configuration content included in each configuration type is supported; or the first network supports the first request. The requested configuration means that the first network element determines, according to the roaming agreement, that the first network supports the first request sent from the second network.

In a possible implementation, before receiving the authorization indication sent by the third network element, the first network element sends a first notification to the third network element, where the first notification is used to indicate that the third network element sends a request according to the configuration parameter. Configure the terminal device, see S102a-S102b. Optionally, the first notification may include a configuration type of the configuration parameter, and the like.

In a possible implementation manner of the present application, the sending end may be determined by the first network element or the second network element before sending the first request to the terminal device by using the first network element or the first network element and the second network element. Whether the terminal device supports configuring the terminal device through a NAS message.

Optionally, the second network element determines whether the terminal device supports the configuration of the terminal device by using the NAS message, and if the second network element determines that the terminal device supports the configuration by using the NAS message, the first network element sends the first to the first network element. The request, if the second network element determines that the terminal device does not support the configuration by using the NAS message, sends a failure message to the sending end. In the present application, a case where the terminal device supports configuration by using a NAS message is taken as an example, and reference is made to S101d.

It should be understood that if S101c and S101d are included in the present application, the order of executing S101c and S101d is not limited.

Optionally, the first network element determines whether the terminal device supports the configuration of the terminal device by using the NAS message, and if the first network element determines that the terminal device supports the configuration by using the NAS message, the first request is sent to the terminal device, If the first network element determines that the terminal device does not support the configuration by using the NAS message, the first network element sends a failure message to the sending end. In the present application, a case where the terminal device supports configuration by using a NAS message is taken as an example, and reference is made to S101d'.

In the present application, the foregoing manner is performed on the first network element to determine that the terminal device supports the configuration of the terminal device by using the NAS message, and the terminal device determines that the first network element supports the configuration of the terminal device by using the NAS message.

In the present application, it is not determined for the first network element whether the terminal device can support the configuration of the terminal device by using the NAS message, and the terminal device is not sure whether the first network element can support the configuration of the terminal device by using the NAS message, first. The network element can negotiate with the terminal device to configure the terminal device through the NAS message.

In a possible implementation, the first network element determines that the terminal device supports the configuration of the terminal device by using the NAS message, and the first network element receives the first indication from the terminal device, where the first network element determines according to the first indication. The terminal device supports configuration of the terminal device through NAS messages, see S103a. The first indication is used to indicate that the terminal device supports configuring the terminal device by using the NAS message.

In a possible implementation manner, after the first network element determines that the terminal device supports the configuration of the terminal device by using the NAS message, the method further includes: the first network element sends a second indication to the terminal device, and refer to S103b. The second indication is used to indicate that the first network supports configuring the terminal device by using the NAS message.

Optionally, the terminal device may send a first indication to the first network element and receive a second indication from the first network element, and correspondingly, the first network element, in a process of network discovery before accessing the first network. Receiving a first indication from the terminal device and sending a second indication to the terminal device in a process of network discovery before the terminal device accesses the first network; or, the terminal device is in the process of authenticating with the first network element, Sending a first indication to the first network element, and receiving a second indication from the first network element. Correspondingly, the first network element receives the first indication from the terminal device during the authentication process with the terminal device, and The terminal device sends a second indication; or, the terminal device sends a first indication to the first network element during the registration process with the first network element, and receives a second indication from the first network element, correspondingly, the first network The UE receives the first indication from the terminal device during the registration process with the terminal device, and sends a second indication to the terminal device.

The process of configuring the terminal device through the NAS message in the first network element and the terminal device in the present application is described in the following with reference to FIG. 5 to FIG.

FIG. 5 is a flowchart of a method for negotiating a terminal device by using a NAS message according to an embodiment of the present disclosure. In FIG. 5, the terminal device is a CPE, the first network is an NHN network, and the second network is a 3GPP network. For example, the process in which the first network element provided by the embodiment of the present application negotiates with the terminal device to configure the terminal device through the NAS message is described. The NH MME network element is an implementation manner of the first network element, and the CPE accesses the NH MME network element by using the access network element, and the access network element may be a base station or the like.

It should be understood that FIG. 5 is an example of applying the method for configuring a terminal device through a NAS message to the interworking architecture of the NHN network and the 4G network shown in FIG. 1 .

The method shown in Figure 5 includes the following steps:

S201: The access network element broadcasts information to the CPE.

S202: The CPE detects the NHN network and additional information needed.

S203: The CPE establishes an RRC connection with the access network element.

S204: The CPE sends a first indication to the NH MME.

In the method shown in FIG. 5, the CPE sends a first indication to the NH MME through the NAS message. Optionally, the CPE may carry the first indication to the existing NAS message, or send the first indication to the NH MME by using a new NAS message.

S205: The NH MME sends a second indication to the CPE.

Similarly, the NH MME sends a second indication to the CPE through the NAS message. Optionally, the NH MME may carry the second indication to the existing NAS message, or send a second indication to the CPE by using a new NAS message.

It should be understood that the method CPE shown in FIG. 5 is to negotiate the configuration of the CPE through the NAS message during the network discovery process before accessing the NHN network.

It should be noted that, if the NHN network supports configuring the terminal device through the NAS message, the terminal device preferentially selects the NHN network that supports configuring the terminal device through the NAS message when selecting the network.

FIG. 6 is a flowchart of a method for negotiating a terminal device by using a NAS message according to an embodiment of the present application. In FIG. 6, the terminal device is a CPE, the first network is an NHN network, and the second network is a 3GPP network. For example, the process in which the first network element provided by the embodiment of the present application negotiates with the terminal device to configure the terminal device through the NAS message is described. The NH MME network element is an implementation manner of the first network element, and the HSS network element is an implementation manner of the second network element. The CPE accesses the NH MME network element by using the access network element, and the access network element may be Equipment such as base stations.

It should be understood that FIG. 6 is an example of applying the method for configuring a terminal device through a NAS message to the interworking architecture of the NHN network and the 4G network shown in FIG. 1 .

The method shown in Figure 6 includes the following steps:

S301: The CPE sends an attach request that carries the first indication to the access network element.

S302: The access network element sends an attach request carrying the first indication to the NH MME.

Optionally, after receiving the attach request that is sent by the CPE and carrying the first indication, the NH MME may determine, according to the first indication, that the CPE supports configuring the CPE by using the NAS message, and the NH MME determines that the CPE and the NHN network support the CPE by using the NAS message. This information can be stored.

S303: The NH MME sends a first indication to the HSS.

Optionally, the NH MME sends the first indication configured by the NAS message to the HSS in the authentication and authorization process. In a possible implementation, the NH MME may carry a first indication in a Diameter or Radius message sent to the Local AAA proxy, and the Local AAA proxy sends the first indication to the Diameter or Radius message via the 3GPP AAA/PSP AAA. HSS. The sending of the first indication by the NH MME to the HSS also indicates that the NHN network itself also supports configuration via NAS messages.

S304: A session establishment process in the NHN network.

S305: The NH MME sends an attach accept message carrying the second indication to the CPE.

Optionally, the confirmation message of the NH MME for the first indication may also be carried in the attach accept message.

In a possible implementation, the NH MME sends an attach accept message carrying the second indication to the CPE, which may be sent to the access NE and then forwarded by the access NE to the CPE.

It should be understood that if the CPE needs to establish a user plane channel to the 3GPP EPS system, the NH MME may also send a first indication to the HSS in the process of establishing a user plane channel to the 3GPP EPS system by the CPE. For example, in the interworking mode in which the NHN network is connected to the 4G network through the ePDG, the CPE may carry the first indication in the IKEv2 message and send it to the ePDG in the process of establishing an IPSec tunnel with the ePDG, and then the ePDG is in the Diameter or Radius message. It is sent to the HSS via 3GPP AAA/PSP AAA. When the NH GW network element of the NHN network is connected to the PGW network element of the 4G network through the S2a-N interface, in the S304, when the session is established between the NH GW and the PGW, the first session is carried in the Create Session Request message. Instructing, in turn, the PGW to send the first indication to the HSS via the 3GPP AAA/PSP AAA in the Diameter message.

It should be understood that the method CPE shown in FIG. 6 is that the terminal device negotiates the CPE through the NAS message during the authentication or registration process with the first network element.

FIG. 7 is a flowchart of a method for negotiating a terminal device by using a NAS message according to an embodiment of the present application. In FIG. 7, the terminal device is a CPE, the first network is an NHN network, and the second network is a 3GPP network. For example, the process in which the first network element provided by the embodiment of the present application negotiates with the terminal device to configure the terminal device through the NAS message is described. The NH AMF network element is an implementation manner of the first network element, and the UDM network element is an implementation manner of the second network element.

It should be understood that FIG. 7 is an example of applying the method for configuring a terminal device through a NAS message to the interworking architecture of the NHN network and the 5G network shown in FIG. 2 .

The method shown in Figure 7 includes the following steps:

S401: The CPE sends a registration request carrying the first indication to the NH AMF.

S402: The NH AMF sends a registration request carrying the first indication to the AMF.

In the method shown in FIG. 7, after the AMF receives the registration request carrying the first indication, the first indication may be sent to the UDM in the following two manners.

In an implementation manner, referring to S403-S404, the AMF sends a first indication to the UDM during the authentication process.

S403: The AMF sends an authentication request message to the UDM.

The authentication request message carries the first indication and the CPE identification information (for example, the CPE ID), and indicates that the CPE corresponding to the CPE identification information is configured by using the NAS message.

In the method shown in FIG. 7, after receiving the authentication request message including the first indication and the CPE identification information sent by the AMF, the UDM can determine that the CPE corresponding to the CPE identification information is configured by using the NAS message.

S404: The UDM sends an authentication response message to the AMF.

Optionally, the authentication response message carries the acknowledgement information for the first indication.

In another implementation, referring to S403a-S404a, the AMF sends a first indication to the UDM during the registration process.

S403a: The AMF sends an AMF registration request message to the UDM.

The AMF registration request message carries the first indication and the CPE identification information (for example, the CPE ID), and indicates that the CPE corresponding to the CPE identification information is configured by using the NAS message.

S404a: The UDM sends an AMF registration response message to the AMF.

Optionally, the AMF registration response message carries the acknowledgement information for the first indication.

S405: The NH AMF receives the registration response message sent by the AMF.

Optionally, the registration response message may further carry the AMF acknowledgement information for the first indication, indicating that the NHN network supports configuring the CPE by using the NAS message.

S406: The NH AMF sends a registration response message to the CPE.

Optionally, the registration response message may further carry the AMF acknowledgement information for the first indication, indicating that the NHN network supports configuring the CPE by using the NAS message.

It should be understood that the method CPE shown in FIG. 7 is that the terminal device negotiates the CPE through the NAS message during the authentication or registration process with the first network element.

The message transmission method provided by the embodiment of the present application is exemplified in the following with reference to FIG. 8 to FIG.

FIG. 8 is a flowchart of a message transmission method according to an embodiment of the present disclosure. In FIG. 8, the terminal device is a CPE, the first network is an NHN network, the second network is a 3GPP network, and the sending end is a service capability server. (services capability server, SCS)/application server (AS) and the case where the second network element belongs to the second network, for example, the message transmission method provided by the embodiment of the present application is described, and the NH MME network element is implemented by the application. An implementation manner of the first network element in the example, the HSS network element is an implementation manner of the second network element in the embodiment of the present application, and the IWK-SCEF network element is an implementation of the third network element in the embodiment of the present application. The SCEF network element is an implementation manner of the fourth network element in the embodiment of the present application.

It should be understood that FIG. 8 is an example of applying the message transmission method provided in the embodiment of the present application to the interworking architecture of the NHN network and the 4G network shown in FIG. 1 as an example.

The method shown in Figure 8 includes the following steps:

S501: The SCEF receives the first request sent by the SCS/AS.

In the method shown in FIG. 8, after receiving the first request sent by the SCS/AS, the SCEF may determine whether the SCS/AS can perform the configuration requested by the first request for the CPE, and if the SCEF determines that the SCS/AS cannot The CPE performs the configuration requested by the first request, and sends a request failure message to the SCS/AS, where the request failure message may be used to indicate that the SCS/AS may not perform the configuration requested by the first request on the CPE, if the SCEF determines the SCS/AS The configuration requested by the first request may be performed on the CPE, and the first request is sent to the HSS. This application uses the SCEF to determine the case where the SCS/AS can perform the configuration requested by the CPE for the first request, as described in S502-S503.

S502: The SCEF determines that the SCS/AS can perform the configuration requested by the first request for the CPE.

S503: The SCEF sends a first request to the HSS.

S504: The HSS determines whether the NHN network supports the configuration requested by the first request.

In the method shown in FIG. 8, after receiving the first request sent by the SCEF, the HSS determines whether the NHN network supports the configuration requested by the first request, and if the HSS determines that the NHN network supports the configuration requested by the first request, executing S505, If the HSS determines that the NHN network does not support the configuration requested by the first request, it sends a failure message to the SCS/AS, and the case where the NHN network does not support the configuration requested by the first request is not shown in the present application.

For example, the SCS/AS requests to configure a new service, and the HSS determines whether the new service is already supported within the NHN network; or, the HSS determines whether the NHN network allows the third party to configure the configured policy type.

S505: The HSS determines, according to the identifier information of the CPE included in the first request, that the CPE is in the NHN network, and sends a first request to the 3GPP AAA.

S506: The 3GPP AAA sends a first request to the Local AAA proxy.

S507: The Local AAA proxy sends the first request to the NH MME.

S508: The NH MME sends a response message to the Local AAA proxy for the first request.

S509: The Local AAA proxy sends a response message to the 3GPP AAA for the first request.

In the method shown in FIG. 8, the first request is sent to the NH MME in the re-authentication process initiated by the 3GPP AAA, and the response message sent by the NH MME is received as an example. In actual applications, the NH MME may also be sent through other processes. The first request, and the response message sent by the NH MME, are not limited in this application.

It should be understood that the response message for the first request may include the confirmation information of the NH MME for the first request, for example, the confirmation message may indicate that the first request is acknowledged.

S510: The 3GPP AAA sends a response message to the HSS for the first request.

S511: The HSS sends a response message to the SCEF for the first request.

S512: The SCEF sends a response message to the SCS/AS for the first request.

In the method shown in FIG. 8, after receiving the response message for the first request sent by the NH MME, the 3GPP AAA sends the response message to the SCS/AS through the HSS and the SCEF.

S513: The NH MME sends a first notification to the IWK-SCEF.

In the present application, the first notification is a notification that the SCS/AS requests to configure the CPE according to the configuration parameter.

S514: The NH MME receives the authorization indication sent by the IWK-SCEF.

In the present application, the authorization indication is used to indicate that the NHN network supports the configuration requested by the first request.

It should be understood that S513-S514 in the present application is an optional step, and the NH MME may directly forward the received first request to the CPE after receiving the first request, and may also, after performing S513-S514, to the CPE. The first request received is forwarded, which is not limited in this application.

S515: The NH MME sends a first request to the CPE by using a NAS message.

S516: The NH MME receives the first response sent by the CPE for the first request.

In the method shown in FIG. 8, after receiving the first response sent by the CPE, the NH MME may send the first response to the SCS/AS in two ways. For an implementation manner, referring to S517a-S517e, the NH MME sends a first response to the SCS/AS through the Local AAA proxy, the 3GPP AAA, the HSS, and the SCEF. For another implementation, refer to S518a-S518c. The NH MME sends a first response to the SCS/AS through the IWK-SCEF and the SCEF.

In the method shown in FIG. 8, the first response includes one or more of the following information: the CPE confirms the first request, the CPE identification information (for example, the CPE ID), and the SCEF identification information (for example, SCEF ID), SCEF reference identification information (for example, SCEF reference ID) and status information of the CPE.

In a possible implementation manner, for the first request sent by the SCS/AS, the CPE needs to report its own state, status change, or statistical data for a period of time. In this scenario, the first response sent by the CPE may be The CPE ID, the SCEF ID, the SCEF reference ID, and the CPE status information may be optionally included, and may also include the CPE confirming the first request.

FIG. 9 is a flowchart of still another method for transmitting a message according to an embodiment of the present application. In FIG. 9, the terminal device is a CPE, the first network is an NHN network, the second network is a 3GPP network, and the sending end is an SCS/ The case where the AS and the second network element belong to the second network is taken as an example, and the message transmission method provided by the embodiment of the present application is described. The NH AMF network element is an implementation manner of the first network element in the embodiment of the present application, and the UDM network element is used. Or the PCF network element is an implementation manner of the second network element in the embodiment of the present application. The IWK-NEF network element is an implementation manner of the third network element in the embodiment of the present application, where the NEF network element is the embodiment of the present application. An implementation of the fourth network element.

It should be understood that FIG. 9 is an example of applying the message transmission method provided by the embodiment of the present application to the interworking architecture of the NHN network and the 5G network shown in FIG. 2 .

The method shown in Figure 9 includes the following steps:

S601: The NEF receives the first request sent by the SCS/AS.

In the method shown in FIG. 9, after receiving the first request sent by the SCS/AS, the NEF can determine whether the SCS/AS can perform the configuration requested by the first request on the CPE, and if the NEF determines that the SCS/AS cannot The CPE performs the configuration requested by the first request, and sends a request failure message to the SCS/AS, where the request failure message can be used to indicate that the SCS/AS cannot perform the configuration requested by the first request for the CPE, if the NEF determines the SCS/AS The configuration requested by the first request may be performed on the CPE, and the first request is sent to the UDM or PCF. The present application is described by the NEF as an example in which the SCS/AS can perform the configuration requested by the first request to the CPE, and refer to S602, S603, and S603a.

S602: The NEF determines that the SCS/AS can perform the configuration requested by the first request for the CPE.

S603: The NEF sends the first request to the UDM.

In the method shown in FIG. 9, after receiving the first request sent by the NEF, the UDM determines whether the NHN network supports the configuration requested by the first request, and if the UDM determines that the NHN network supports the configuration requested by the first request, and according to the first If the CPE is identified in the request, and the CPE is determined to be in the NHN network, S604 is performed.

S604: The UDM sends a first request to the AMF.

It should be understood that in the method shown in FIG. 9, the AMF is an AMF registered with the CPE.

S603a: The NEF sends a first request to the PCF.

In the method shown in FIG. 9, after receiving the first request sent by the NEF, the PCF determines whether the NHN network supports the configuration requested by the first request, and if the PCF determines that the NHN network supports the configuration requested by the first request, and according to the first The identification information of the CPE included in the request determines that the CPE is in the NHN network, and then executes S604a.

S604a: The PCF sends a first request to the AMF.

It should be understood that S603-S604 and S603a-S604a are only selected in one mode, and the user can decide which way to deploy according to the configuration.

S605: The AMF sends a first request to the NH AMF.

In the method shown in FIG. 9, the AMF can query the NH AMF of the current NHN network according to the NH AMF at the time of CPE registration.

S606: The NH AMF sends a response message to the AMF for the first request.

It should be understood that the response message sent by the NH AMF to the AMF for the first request is different from the first response in the application, and the response message may include the AMF confirming the first request, for example, the confirmation message may indicate the confirmation. Received the first request.

It should be understood that, corresponding to S603-S604 and S603a-S604a, two methods for sending a first request to the AMF, the AMF in FIG. 9 may respond to the NEF in two ways correspondingly, and a way of replying the response is shown in S607- S608, another way of replying to the response is referred to S607a-S608a.

S607: The AMF sends a response message to the UDM for the first request.

S608: The UDM sends a response message to the NEF for the first request.

It should be understood that the manner in which the response is replied in S607-S608 corresponds to the manner in which S603-S604 sends the first request.

S607a: The AMF sends a response message to the PCF for the first request.

S608a: The PCF sends a response message to the NEF for the first request.

It should be understood that the manner in which the responses are replied in S607a-S608a corresponds to the manner in which S603a-S604a sends the first request.

S609: The NEF sends a response message to the SCS/AS for the first request.

S610: The NH AMF sends a first notification to the IWK-NEF.

In the present application, the first notification is a notification that the SCS/AS requests to configure the CPE according to the configuration parameter.

S611: The NH AMF receives the authorization indication sent by the IWK-NEF.

In the present application, the authorization indication is used to indicate that the NHN network supports the configuration requested by the first request.

It should be understood that S610-S611 in the present application is an optional step, and the AMF may directly forward the received first request to the CPE after receiving the first request, and may also forward to the CPE after executing S610-S611. The first request received is not limited in this application.

S612: The NH AMF sends a first request to the CPE through the NAS message.

Optionally, the NAS message may be a new NAS message, or may be a NAS message obtained by modifying an existing NAS message. For example, an existing indication may be added to the existing NAS message to indicate the modified NAS. The message carries the first request.

Optionally, if the NAS message is a new NAS message, the NH MME may separately send the NAS message to the CPE, or may carry the NAS message in the NAS message that is being sent to the CPE at that time.

S613: The NH AMF receives the first response sent by the CPE through the NAS message for the first request.

In the method shown in FIG. 9, after the NH AMF receives the first response sent by the CPE, the first response can be sent to the SCS/AS in three ways. For an implementation, refer to S614a-S614d. The NH AMF sends a first response to the SCS/AS through the AMF, UDM, and NEF. For another implementation, refer to S615a-S615d. The NH AMF sends the SSC/AS to the SCS/AS through the AMF, PCF, and NEF. One response, yet another implementation refers to S616a-S616c, and the NH AMF sends a first response to the SCS/AS through the IWK-NEF and the NEF.

In the method shown in FIG. 9, the first response includes one or more of the following information: the CPE confirms the first request, the CPE ID, the NEF identification information (for example, the NEF ID), and the NEF reference identifier. Information (for example, NEF reference ID) and status information of the CPE.

In a possible implementation manner, for the first request sent by the SCS/AS, the CPE needs to report its own state, status change, or statistical data for a period of time. In this scenario, the first response sent by the CPE may be The CPE ID, the NEF ID, the NEF reference ID, and the status information of the CPE are optional. Optionally, the CPE can also include the confirmation information of the first request.

In the embodiment of the present application, the method shown in FIG. 9 is also applicable to the network architecture shown in FIG. 3. When the method shown in FIG. 9 is applied to the network architecture shown in FIG. 3, the NH AMF in FIG. 9 is replaced by N3IWF. The NAS message in S612-S613 is transmitted by the IKEv2 message or transmitted on the IPSec channel, and the interaction steps between the NH AMF and the AMF in FIG. 9 are forwarded by the Local AAA proxy and the N3IWF.

In various embodiments of the present application, the foregoing describes that the configuration of the terminal device is implemented by interworking between the NHN network and the 3GPP network. In a possible implementation manner, the transmitting end can directly configure the terminal device through the 3GPP network without resorting to the NHN network. For example, in the method shown in FIG. 9, the 3GPP network is used as a 5G network as an example. If the transmitting end directly configures the terminal device through the 5G network, in the method shown in FIG. 9, the NH AMF is a 5G network. The AMF in the middle is equivalent to the interaction between the NH AMF and the AMF network element. Optionally, the IWK SCEF network element exists only in the roaming scene.

FIG. 10 is a flowchart of still another method for transmitting a message according to an embodiment of the present application. In FIG. 10, the terminal device is a CPE, the first network is an NHN network, the second network is a PSP network, and the sending end is an SCS/ The case where the AS and the second network element belong to the second network is taken as an example, and the message transmission method provided by the embodiment of the present application is described. The NH MME network element is an implementation manner of the first network element in the embodiment of the present application, and the PSP AAA network is used. An embodiment of the second network element in the embodiment of the present application, the IWK-SCEF network element is an implementation manner of the third network element in the embodiment of the present application, and the SCEF network element is the fourth network in the embodiment of the present application. An implementation of meta.

It should be understood that FIG. 10 is an example of applying the message transmission method provided in the embodiment of the present application to the interworking architecture of the NHN network and the 4G network shown in FIG. 1 as an example.

The method shown in Figure 10 includes the following steps:

S701: The SCEF receives the first request sent by the SCS/AS.

In the method shown in FIG. 10, after receiving the first request sent by the SCS/AS, the SCEF may determine whether the SCS/AS can perform the configuration requested by the first request for the CPE, and if the SCEF determines that the SCS/AS cannot The CPE performs the configuration requested by the first request, and sends a request failure message to the SCS/AS, where the request failure message may be used to indicate that the SCS/AS may not perform the configuration requested by the first request on the CPE, if the SCEF determines the SCS/AS The configuration requested by the first request may be performed on the CPE, and the first request is sent to the PSP AAA. The present application uses the SCEF to determine, as an example, a case where the SCS/AS can perform the configuration requested by the first request to the CPE, and refer to S702-S703.

S702: The SCEF determines that the SCS/AS can perform the configuration requested by the first request for the CPE.

S703: The SCEF sends the first request to the PSP AAA.

S704: The PSP AAA determines whether the NHN network supports the configuration requested by the first request.

In the method shown in FIG. 10, after receiving the first request sent by the SCEF, the PSP AAA determines whether the NHN network supports the configuration requested by the first request, and if the PSP AAA determines that the NHN network supports the configuration requested by the first request, and according to The identification information of the CPE included in the first request determines that the CPE is in the NHN network, and executes S705.

S705: The PSP AAA sends a first request to the NH MME.

It should be understood that the method shown in FIG. 10 is applied to a scenario in which PSP AAA and Local AAA proxy are integrated. If the PSP AAA and the Local AAA proxy are independent network elements, the PSP AAA may send the first request to the NH MME through the Local AAA proxy, that is, the PSP AAA sends the first request to the Local AAA proxy, and then the Local AAA proxy A request is forwarded to the NH MME.

Optionally, when the PSP AAA sends the first request to the NH MME, the PSP AAA may carry a third indication, where the third indication is used to indicate that the first request is from the first network.

S706: The NH MME sends a response message to the PSP AAA for the first request.

It should be understood that the response message sent by the NH MME to the PSP AAA for the first request may be different from the first response in the application, and the response message may include the AMF confirming information about the first request, for example, the acknowledgement message may be Instructs to confirm receipt of the first request.

It should be understood that the method shown in FIG. 10 is applied to a scenario in which PSP AAA and Local AAA proxy are integrated. If the PSP AAA and the Local AAA proxy are independent network elements, the NH MME may send the first request to the PSP AAA through the Local AAA proxy, that is, the NH MME sends the first request to the Local AAA proxy, and then the Local AAA proxy A request is forwarded to the PSP AAA.

In the method shown in FIG. 10, in the re-authentication process initiated by the PSP AAA, the first request is carried in the message sent by the re-authentication process, and the first request is sent to the NH MME, and the response message sent by the NH MME is received as an example. In actual application, the PSP AAA may also send a first request to the NH MME through a message in other communication processes, and receive a response message sent by the NH MME. Of course, the first request may be used as a new one without using the existing communication process. The message is sent to the NH MME, which is not limited in this application.

S707: The PSP AAA sends a response message to the SCEF for the first request.

S708: The SCEF sends a response message to the SCS/AS for the first request.

In the method shown in FIG. 10, after receiving the response message for the first request sent by the NH MME, the PSP AAA sends the response message to the SCS/AS through the SCEF.

S709: The NH MME sends a first notification to the IWK-SCEF.

In the present application, the first notification is a notification that the SCS/AS requests to configure the CPE according to the configuration parameter.

S710: The NH MME receives an authorization indication sent by the IWK-SCEF.

In the present application, the authorization indication is used to indicate that the NHN network supports the configuration requested by the first request.

It should be understood that, in this application, S709-S710 is an optional step, and the NH MME may directly forward the received first request to the CPE after receiving the first request, or may, after performing S709-S710, to the CPE. The first request received is forwarded, which is not limited in this application.

S711: The NH MME sends a first request to the CPE by using a NAS message.

S712: The NH MME receives the first response sent by the CPE by using the NAS message for the first request.

In the method shown in FIG. 10, after receiving the first response sent by the CPE, the NH MME may further send a first response to the SCS/AS. Optionally, the first response can be sent to the SCS/AS in two ways. For an implementation manner, referring to S713a-S713c, the NH MME sends a first response to the SCS/AS through the PSP AAA and the SCEF. In another implementation manner, referring to S714a-S714c, the NH MME sends a first response to the SCS/AS through the IWK-SCEF and the SCEF.

It should be understood that the method illustrated in Figure 10 applies to the integration of PSP AAA and Local AAA proxy. If the PSP AAA and the Local AAA proxy are independent network elements, the first response in S713a can be sent to the PSP AAA through the Local AAA proxy, and then sent by the PSP AAA to the SCEF and sent to the SCS/AS through the SCEF.

In the method shown in FIG. 10, the first response includes one or more of the following information: the CPE confirms the first request, the CPE ID, the SCEF ID, the SCEF reference ID, and the status information of the CPE.

In a possible implementation manner, for the first request sent by the SCS/AS, the CPE needs to report its own state, status change, or statistical data for a period of time. In this scenario, the first response sent by the CPE may be The CPE ID, the SCEF ID, the SCEF reference ID, and the CPE status information may be optionally included, and may also include the CPE confirming the first request.

It should be understood that the network element IWK-SCEF, Local AAA proxy, PSP AAA, and SCEF may be combined or grouped in one or more devices, and the IWK-SCEF, Local AAA proxy, PSP AAA, and SCEF network elements are combined. When a device is used, the interaction between them can be considered as internal operation, that is, the step of being set up between the network elements of one device can be omitted. In this case, the IWK-SCEF, Local AAA proxy, which is set in one device, The PSP AAA and the SCEF network element may be equivalent to the second network element in this application. Of course, in some application scenarios, the NH MME, the IWK-SCEF, the Local AAA proxy, the PSP AAA, and the SCEF network element may also be combined in one device. In this case, the first network element and the second network element are the same device. The devices are composed of NH MME, IWK-SCEF, Local AAA proxy, PSP AAA, and SCEF network elements.

In the embodiment of the present application, the method shown in FIG. 10 is also applicable to the network architecture shown in FIG. 2. When the method shown in FIG. 10 is applied to the network architecture shown in FIG. 2, the network element NH MME in FIG. Instead of the NH AMF, the IWK-SCEF is replaced by the IWK-NEF, and the SCEF is replaced by the NEF. Referring to FIG. 11, in FIG. 11, S801-S814c respectively perform the same operations as S701-S714c in FIG. 10, and details are not described herein again.

FIG. 12 is a flowchart of still another method for transmitting a message according to an embodiment of the present application. In FIG. 12, the terminal device is a CPE, the first network is an NHN network, and the second network is a 3GPP network or a PSP network, and the sending end is used. The message transmission method provided by the embodiment of the present application is described as an example in which the SCS/AS and the second network element belong to the second network. The NH MME network element is an implementation manner of the first network element in the embodiment of the present application, and the SCEF network element is an implementation manner of the second network element in the embodiment of the present application.

It should be understood that FIG. 12 illustrates an example in which the message transmission method provided by the embodiment of the present application is applied to an interworking architecture of an NHN network and a 4G network, or an architecture in which an NHN network and a PSP network communicate with each other. When applied to the interworking architecture of the NHN network and the 4G network, the HSS network element shown in FIG. 12 corresponds to the PSP AAA network element shown in FIG. 12 when applied to the architecture of the interworking between the NHN network and the PSP network.

It should be understood that FIG. 12 is an example of applying the message transmission method provided by the embodiment of the present application to the interworking architecture of the NHN network and the 4G network shown in FIG. 1 as an example.

The method shown in Figure 12 includes the following steps:

S901: The SCEF receives the first request sent by the SCS/AS.

In the method shown in FIG. 12, after receiving the first request sent by the SCS/AS, the SCEF may determine whether the SCS/AS can perform the configuration requested by the first request for the CPE, and if the SCEF determines that the SCS/AS cannot The CPE performs the configuration requested by the first request, and sends a request failure message to the SCS/AS, where the request failure message may be used to indicate that the SCS/AS may not perform the configuration requested by the first request on the CPE, if the SCEF determines the SCS/AS The configuration requested by the first request may be performed on the CPE, and the first request is sent to the HSS/PSP AAA. The present application uses the SCEF to determine, as an example, a case where the SCS/AS can perform the configuration requested by the CPE for the first request, and refer to S902-S903.

S902: The SCEF determines that the SCS/AS can perform the configuration requested by the first request for the CPE.

S903: The SCEF sends a first request to the HSS/PSP AAA.

It should be understood that, in the method shown in FIG. 12, the SCEF may send a first request to the HSS/PSP AAA during the signing process. Optionally, the message carrying the first request in the signing process may be sent to the HSS/PSP AAA. Of course, it can also be sent in other processes, and can also be sent to the HSS/PSP AAA by using a new message, which is not limited in this application.

S904: The HSS/PSP AAA determines whether the NHN network supports the configuration requested by the first request.

S905: The HSS/PSP AAA sends a response message to the SCEF for the first request.

In the method shown in FIG. 12, after the HSS/PSP AAA determines whether the NHN network supports the configuration requested by the first request, the HSS/PSP AAA may send the message to the SCEF if it determines that the NHN network does not support the configuration requested by the first request. The response message carries the request failure message. If it is determined that the NHN network supports the configuration requested by the first request, the response message sent to the SCEF may be carried in the response message, and may also carry the NHN network information where the CPE is currently located, for example, the CPE current The information of the NHN network where the CPE is located may include the identifier of the IWK-SCEF of the NHN network where the CPE is currently located, the identifier of the NH MME, or the identifier of the NHN network where the CPE is currently located.

After the SCEF receives the response message for the first request sent by the HSS/PSP AAA, if it is determined that the NHN network supports the configuration requested by the first request, the SCN may determine the current NHN network where the CPE is located according to the current NHN network information of the CPE. Execute S906.

S906: The SCEF sends a first request to the IWK-SCEF.

S907: The IWK-SCEF sends the first request to the NH MME.

S908: The NH MME sends a response message to the IWK-SCEF for the first request.

In the method shown in FIG. 12, after receiving the response message for the first request sent by the NH MME, the IWK-SCEF sends the response message to the SCS/AS through the SCEF.

It should be understood that the response message sent by the NH MME to the IWK-SCEF for the first request may include the confirmation information of the NH MME for the first request, for example, the confirmation message may indicate that the first request is acknowledged.

S909: The IWK-SCEF sends a response message to the SCEF for the first request.

S910: The SCEF sends a response message to the SCS/AS for the first request.

S911: The NH MME sends a first request to the CPE through the NAS message.

S912: The NH MME receives the first response sent by the CPE by using the NAS message for the first request.

In the method shown in FIG. 12, after receiving the first response sent by the CPE, the NH MME may send the first response to the SCS/AS in the same manner as in FIG. 8-11. Figure 12 shows only two of these implementations, see S913a-S913c and S914a-S914c.

In the embodiment of the present application, the method shown in FIG. 12 is also applicable to the network architecture shown in FIG. 2. When the method shown in FIG. 12 is applied to the network architecture shown in FIG. 2, the network element NH MME in FIG. Instead of NH AMF, IWK-SCEF is replaced by IWK-NEF, SCEF is replaced by NEF, and HSS is replaced by UDM/PSP AAA. Referring to FIG. 13, in FIG. 13, S1001-S1014c are executed in the same manner as S901-S914c in FIG. 12, respectively. Operation will not be repeated here.

The foregoing provides a description of the solution provided by the present application from the perspective of interaction between the various network elements. It can be understood that, in order to implement the above functions, each of the foregoing network elements includes a hardware structure and/or a software module corresponding to each function. Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

FIG. 14 shows a possible exemplary block diagram of a device involved in the embodiment of the present invention. The device 1400 may exist in the form of software, or may be a terminal device or a first network. The element or the second network element may also be a chip in the terminal device or a chip in the first network element or a chip in the second network element. The device 1400 includes a processing unit 1402 and a communication unit 1403. The processing unit 1402 is configured to perform control management on the action of the device 1400. For example, when the device 1400 is a terminal device, the processing unit 1402 is configured to perform a technical process of determining a first response according to the first request, when the device 1400 is the first The processing unit 1402 is configured to perform the process of carrying the first request in the NAS message, and is also used to perform the technical process of S101d' in FIG. 4. When the device 1400 is the second network element, the processing unit 1402 is used by the processing unit 1402. The technical processes such as S101c and S101d in Fig. 4 are executed. Communication unit 1403 is used to support communication of device 1400 with other network entities. When the device 1400 is a terminal device, the communication unit 1403 can be used to support the device 1400 to perform technical processes such as S102, S103, S103a, and S103b in FIG. 4. When the device 1400 is the first network element, the communication unit 1403 can be used to support the device 1400. The technical processes of S102, S103, S103a, S103b, S101, S101b, S101a', S102a, S102b, S104a, and S105a in FIG. 4 are performed. When the device 1400 is the second network element, the communication unit 1403 can be used to support the device 1400 to execute. Technical processes such as S101a, S103a3, S101b, S101a', S101b', and S104b in FIG. The device 1400 can also include a storage unit 1401 for storing program codes and data of the device 1400.

The processing unit 1402 may be a processor or a controller, for example, a general central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), and an application specific integrated Circuits, ASICs, field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication unit 1403 may be a communication interface, a transceiver, a transceiver circuit, or the like. The storage unit 1401 may be a memory.

When the processing unit 1402 is a processor, the communication unit 1403 is a transceiver, and the storage unit 1401 is a memory, the apparatus 1400 according to the embodiment of the present invention may be the apparatus shown in FIG.

FIG. 15 is a schematic diagram showing a possible logical structure of an apparatus involved in the foregoing embodiment provided by an embodiment of the present application. As shown in FIG. 15, the apparatus 1500 can include at least one processor 1501. In the embodiment of the present application, the processor 1501 is configured to control and manage the action of the device. Optionally, the device may further include a memory 1502, the transceiver 1503. The processor 1501, the transceiver 1503, and the memory 1502 may be connected to each other or to each other through a bus 1504. The memory 1502 is configured to store code and data of the device. Transceiver 1503 is used to support the device for communication.

The following is a detailed introduction to the various components of the device:

The processor 1501 is a control center of the device, and may be a processor or a collective name of a plurality of processing elements. For example, the processor 1501 is a CPU, which may be implemented by an ASIC, or one or more integrated circuits configured to implement an embodiment of the present invention, such as one or more DSPs, or one or more FPGA.

The processor 1501 can perform various functions of the apparatus 1500 by running or executing a software program stored in the memory 1502 and calling data stored in the memory 1502.

The memory 1502 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this. The memory 1502 can exist independently and is coupled to the processor 1501 via a communication bus 1504. The memory 1502 can also be integrated with the processor 1501.

The transceiver 1503 uses a device such as any transceiver for communication with other nodes, such as a first network element. It can also be used to communicate with a communication network, such as Ethernet, radio access network (RAN), Wireless Local Area Networks (WLAN), and the like. The transceiver 1203 may include a receiving unit to implement a receiving function, and a transmitting unit to implement a transmitting function.

The communication bus 1504 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 15, but it does not mean that there is only one bus or one type of bus.

The device structure illustrated in Figure 15 does not constitute a limitation to the device, and may include more or fewer components than those illustrated, or some components may be combined, or different component arrangements.

When the device shown in FIG. 15 is a terminal device or a chip in the terminal device, the following steps can also be performed:

In a possible implementation, the transceiver 1503 is configured to receive a first request from a first network element, where the first request is a request from a sending end, and the first request includes a configuration parameter, where a request for requesting configuration of the device according to the configuration parameter; a processor 1501, configured to determine a first response according to the first request; the transceiver 1503, further configured to pass a non-access stratum NAS message Sending the first response to the first network element, where the first network element belongs to the first network.

In a possible implementation, the first response includes one or more of the following information: the device confirms the first request, the identifier information of the device, and the fourth network element. The identification information, the reference identification information of the fourth network element, and the status information of the device, where the fourth network element belongs to the second network.

In a possible implementation manner, the transceiver 1503 is further configured to:

Before receiving the first request sent by the first network element, sending a first indication to the first network element, where the first indication is used to indicate that the apparatus supports configuring the apparatus by using a NAS message.

In a possible implementation manner, the transceiver 1503 is further configured to:

After transmitting the first indication to the first network element, receiving a second indication from the first network element, the second indication is used to indicate that the first network supports configuring the device by using a NAS message.

In a possible implementation manner, the transceiver 1503 is specifically configured to:

Transmitting, by the first network element, the first indication, and receiving the second indication from the first network element, in a process of network discovery before accessing the first network; or Transmitting, by the first network element, the first indication to the first network element, and receiving the second indication from the first network element, or in the first During the registration process, the network element sends the first indication to the first network element and receives the second indication from the first network element.

In a possible implementation manner, the first network is an NHN network, and the second network is a 3GPP network or a PSP network.

The embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the message transmission apparatus shown in FIG. 14 and FIG. 15 above, which includes program code for executing the foregoing method embodiment. The transmission of the message can be achieved by executing the stored program code.

The embodiment of the present application also provides a computer program product. The computer program product includes computer software instructions that are loadable by a processor to implement the methods of the above method embodiments.

The embodiment of the present application further provides a chip, which includes a processor and a transceiver component, and optionally, a storage unit, which can be used to perform the method of the foregoing embodiment of the present application.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.

The various illustrative logic units and circuits described in the embodiments of the present application may be implemented by a general purpose processor, a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device. Discrete gate or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the functions described. A general purpose processor may be a microprocessor. Alternatively, the general purpose processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.

The steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two. The software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art. Illustratively, the storage medium can be coupled to the processor such that the processor can read information from the storage medium and can write information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and the storage medium may be disposed in the ASIC, and the ASIC may be disposed in the terminal device. Alternatively, the processor and the storage medium may also be disposed in different components in the terminal device.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the invention has been described with respect to the specific embodiments and embodiments thereof, various modifications and combinations may be made without departing from the spirit and scope of the invention. Accordingly, the specification and drawings are to be construed as the It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims (33)

A message transmission method, comprising: Receiving, by the first network element, the first request from the sending end, where the first request includes a configuration parameter, where the first request is used to request to configure the terminal device according to the configuration parameter, where the first network element belongs to the first a network The first network element sends the first request to the terminal device by using a non-access stratum NAS message. The method according to claim 1, wherein after the first network element sends the first request to the terminal device by using a NAS message, the method further includes: The first network element receives a first response from the terminal device for the first request. The method of claim 2, further comprising: The first network element sends the first response to the sending end by using a third network element and a fourth network element, where the third network element belongs to the first network, and the fourth network element belongs to Second network; or, The first network element sends the first response to the sending end by using the second network element, where the second network element belongs to the first network or belongs to the second network. The method according to claim 2 or 3, wherein the first response includes one or more of the following information: confirmation information of the first request by the terminal device, the terminal device The identification information, the identification information of the fourth network element, the reference identification information of the fourth network element, and the status information of the terminal device. The method according to claim 3 or 4, wherein before the first network element sends the first request to the terminal device, the method further includes: The first network element receives an authorization indication from a third network element, where the authorization indication is used to indicate that the first network supports the configuration requested by the first request. The method according to any one of claims 1 to 5, wherein the first network element receives the first request from the transmitting end, including: The first network element receives the first request by using a second network element. The method according to any one of claims 1 to 6, wherein before the first network element sends the first request to the terminal device, the method further includes: The first network element determines that the terminal device supports configuring the terminal device by using a NAS message. The method according to claim 7, wherein the first network element determines that the terminal device supports configuring the terminal device by using a NAS message, including: The first network element receives a first indication from the terminal device, where the first indication is used to indicate that the terminal device supports configuring the terminal device by using a NAS message; The first network element determines, according to the first indication, that the terminal device supports configuring the terminal device by using a NAS message. The method according to claim 8, wherein after the determining that the terminal device supports the configuration of the terminal device by using a NAS message, the method further includes: The first network element sends a second indication to the terminal device, where the second indication is used to indicate that the first network supports configuring the terminal device by using a NAS message. The method of claim 9 further comprising: Receiving, by the first network element, the first indication from the terminal device, and transmitting the second identifier to the terminal device, in a process of network discovery before the terminal device accesses the first network Indication; or, Receiving, by the first network element, the first indication from the terminal device in an authentication process with the terminal device, and sending the second indication to the terminal device; or The first network element receives the first indication from the terminal device during registration with the terminal device, and sends the second indication to the terminal device. The method according to any one of claims 1 to 10, wherein the first network is a neutral deployment network NHN, and the second network is a third generation partnership project 3GPP network or a service provider PSP network. A message transmission method, comprising: The second network element receives the first request from the sending end, where the first request includes the configuration parameter and the identifier information of the terminal device, where the first request is used to request to configure the terminal device according to the configuration parameter; Determining, by the second network element, that the terminal device is in the first network, according to the identifier information of the terminal device, sending the first request to the first network element, where the first network element belongs to the First network. The method according to claim 12, wherein the second network element belongs to the first network or belongs to the second network. The method according to claim 13, wherein the second network element belongs to the first network; The first request further includes a third indication, the third indication being used to indicate that the first request is from the first network. The method according to any one of claims 12 to 14, wherein before the sending, by the second network element, the first request to the first network element, the method further includes: The second network element determines a configuration requested by the first network to support the first request. The method of claim 15, wherein the configuration parameters comprise at least one configuration type, the configuration types including configuration and configuration updates, software firmware management, status and performance monitoring, and diagnostics, each configuration type including Different configuration content; Determining, by the second network element, the configuration requested by the first network to support the first request, including: The second network element determines that the first network supports the at least one configuration type, and supports different configuration content included in each configuration type. The method according to any one of claims 12 to 16, wherein before the sending, by the second network element, the first request to the first network element, the method further includes: The second network element determines that the terminal device supports configuring the terminal device by using a non-access stratum NAS message. The method according to any one of claims 12 to 17, wherein after the sending, by the second network element, the first request to the first network element, the method further includes: The second network element receives the first response from the first network element, and sends the first response to the sending end, where the first response is that the terminal device sends the first network element to the first network element. The response to the first request. The method according to claim 18, wherein the first response includes one or more of the following information: the confirmation information of the first request by the terminal device, the identifier of the terminal device The information, the identification information of the fourth network element, the reference identification information of the fourth network element, and the status information of the terminal device, the fourth network element belongs to the second network. The method according to any one of claims 12 to 19, wherein the first network is a neutral deployment network NHN, and the second network is a third generation partnership project 3GPP network or a service provider PSP network. A message transmission method, comprising: Receiving, by the first network element, the first request from the sending end, where the first request includes a configuration parameter, where the first request is used to request to configure the terminal device according to the configuration parameter, where the One network element belongs to the first network; The terminal device sends a first response to the first request to the first network element by using a non-access stratum NAS message. The method according to claim 21, wherein the first response includes one or more of the following information: the confirmation information of the first request by the terminal device, the identifier of the terminal device The information, the identification information of the fourth network element, the reference identification information of the fourth network element, and the status information of the terminal device, the fourth network element belongs to the second network. The method according to claim 21 or 22, wherein before the receiving, by the first network element, the first request from the transmitting end, the terminal device further includes: The terminal device sends a first indication to the first network element, where the first indication is used to indicate that the terminal device supports configuring the terminal device by using a NAS message. The method according to claim 23, wherein after the terminal device sends the first indication to the first network element, the method further includes: The terminal device receives a second indication from the first network element, where the second indication is used to indicate that the first network supports configuring the terminal device by using a NAS message. The method of claim 24, further comprising: Sending, by the terminal device, the first indication to the first network element, and receiving the second indication from the first network element, in a process of network discovery before accessing the first network; or, The terminal device sends the first indication to the first network element and receives the second indication from the first network element in an authentication process with the first network element; or The terminal device sends the first indication to the first network element and receives the second indication from the first network element during registration with the first network element. The method according to any one of claims 21 to 25, wherein the first network is a neutral deployment network NHN, and the second network is a third generation partnership project 3GPP network or a service provider PSP network. A message transmission device, comprising: a transceiver, a memory and a processor; The transceiver is configured to communicate with the device; The memory for storing a computer program; The processor is configured to call and run the computer program from the memory, such that the device performs the message transmission method according to any one of claims 1 to 11. A message transmission device, comprising: a transceiver, a memory and a processor; The transceiver is configured to communicate with the device; The memory for storing a computer program; The processor is configured to call and run the computer program from the memory, such that the device performs the message transmission method according to any one of claims 12 to 20. A message transmission device, comprising: a transceiver, a memory and a processor; The transceiver is configured to communicate with the device; The memory for storing a computer program; The processor is configured to call and run the computer program from the memory such that the apparatus performs the message transmission method of any one of claims 21 to 26. The apparatus according to claim 29, wherein said apparatus is a chip in a terminal device or a terminal device. A computer storage medium, characterized in that the computer storage medium stores instructions that, when run on a computer, cause the computer to perform the method of any of claims 1-11. A computer storage medium, characterized in that the computer storage medium stores instructions that, when run on a computer, cause the computer to perform the method of any one of claims 12-20. A computer storage medium, characterized in that the computer storage medium stores instructions that, when run on a computer, cause the computer to perform the method of any one of claims 21-26.

Images