CN110278095A

CN110278095A - A kind of method for message transmission and device

Info

Publication number: CN110278095A
Application number: CN201810206475.4A
Authority: CN
Inventors: 李欢; 靳维生
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-03-13
Filing date: 2018-03-13
Publication date: 2019-09-24
Also published as: WO2019174582A1

Abstract

A kind of method for message transmission and device.This method comprises: the first network element receives the first request from transmitting terminal, first request includes configuration parameter, first request configures terminal device according to configuration parameter for requesting, first network element belongs to first network, after first network element receives the first request from transmitting terminal, the first request is sent to terminal device by NAS message.When mobile network is applied to vertical industry, it can be configured by the above method for the terminal device for belonging to different vertical industry, without disposing special configuration server for the terminal device for belonging to different vertical industry and establishing special channel, to reduce lower deployment cost and deployment complexity.

Description

Message transmission method and device

Technical Field

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

Background

The multefer alliance provides a multefer technology, which refers to a technology for constructing a new wireless network by independently operating a Long Term Evolution (LTE) technology on an unlicensed spectrum (e.g., a global 5GHz unlicensed spectrum), and in the related art, a wireless network constructed by using the multefer technology is referred to as a Neutral Host Network (NHN).

In the prior art, a terminal device is allowed to directly access a third Generation Partnership Project (3 GPP) core network or a service provider (PSP) network from an access network element in a NHN network, and is also 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, and for convenience of description, the core network of the NHN network is referred to as the NHN core network.

In a scenario that a terminal device accesses a 3GPP core network or a PSP network via an NHN core network, a third-party server generally depends on a specially deployed configuration server to configure the terminal device, and a configuration process depends on a special channel established between the terminal device and the configuration server, when a mobile network is applied to a vertical industry, different configurations may need to be performed for terminal devices belonging to different vertical industries, if a method in the prior art is used, different configuration servers need to be deployed for different vertical industries, and different configuration servers need to establish special channels with corresponding terminal devices, respectively, which may cause problems of high cost and complex deployment.

Disclosure of Invention

The embodiment of the application provides a message transmission method and a message transmission device, which are used for configuring terminal equipment on the basis of not adding a special configuration server.

In order to achieve the above purpose, the embodiments of the present application provide the following technical solutions:

in a first aspect, a message transmission method is provided, including: the first network element receives a first request from a sending end, the first request includes configuration parameters, the first request is used for requesting to configure the terminal device according to the configuration parameters, the first network element belongs to a first network, and after the first network element receives the first request from the sending end, the first network element sends the 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 method, and special configuration servers and special channels do not need to be deployed for the terminal devices belonging to different vertical industries, so that the deployment cost and the deployment complexity are reduced.

Optionally, the configuration parameters may include at least one configuration type, and the configuration type may include configuration and configuration update, software firmware management, status and performance monitoring and diagnosis, and the like, and each configuration type includes different configuration contents. For example, the configuration content included in the software firmware management may be to know the version of the terminal device, load the software module, update the software module, unload the software module, and the like, the configuration content included in the status and performance monitoring may be to monitor the status and performance of the terminal device, and the configuration content included in the diagnosis may be to diagnose the connection and service problem of the terminal device and instruct the terminal device to perform the next operation, and the like.

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

In the application, 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 executes subsequent processing according to the first response of the terminal device. In one possible design, the first network element sends the first response to the sending end through 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 the second network. In another possible design, the first network element sends the first response to the sending end through a second network element, where the second network element belongs to the first network or belongs to the second network.

In one possible design, the first response includes one or more of the following information: the confirmation information of the terminal equipment to the first request, the identification information of the terminal equipment, the identification information of the fourth network element, the reference identification information of the fourth network element and the state information of the terminal equipment.

In a possible design, before the first network element sends the first request to the terminal device, the first network element receives 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.

In this application, how the first network element receives the first request from the transmitting end is not limited. In one possible design, the first network element receives the first request from the sending end through a second network element, and the second network element belongs to the first network or the second network. When a first network element receives a first request from a sending end through a second network element, the second network element firstly receives the first request from the sending end, determines that a terminal device is in a first network according to identification information of the terminal device included in the first request, and then sends the first request to the first network element.

In one 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 indicates that the first request is from the first network.

In one possible design, before the second network element sends the first request to the first network element, it may also be determined that the first network supports the configuration requested by the first request. In the case that the configuration parameters include 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 that the first network supports 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 the terminal device receives the first request from the sending end, it may also be determined that the terminal device supports configuring the terminal device through an NAS message. In one possible design, it is determined by the second network element that the terminal device supports configuring the terminal device by NAS messages.

In another possible design, it is determined by the first network element that the terminal device supports configuring the terminal device by NAS messages. According to the method, the first network element or the second network element sends the first request to the terminal equipment only when the terminal equipment supports the configuration through the NAS message, and the first request is sent to the terminal equipment when the terminal equipment does not support the configuration through the NAS message, so that the sending is failed or wrong, and therefore the failure or wrong receiving when the terminal equipment receives the first request can be avoided through the method.

In one possible design, the first network element may determine that the terminal device supports configuring the terminal device through NAS messages by: the first network element receives a first indication from the terminal device, wherein the first indication is used for indicating that the terminal device supports the configuration of the terminal device through the NAS message, and the first network element determines that the terminal device supports the configuration of the terminal device through the NAS message according to the first indication.

In a possible design, after determining that the terminal device supports configuring the terminal device through the NAS message, the first network element 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 device through the NAS message, so that the terminal device preferentially accesses the first network.

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

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

In a second aspect, a message transmission apparatus is provided, where the apparatus has a function of implementing the first network element in the foregoing method embodiment. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. 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 used for storing computer-executable instructions, the transceiver is used for realizing the communication between the device and other communication entities, the processor is connected with the memory through a bus, and when the device runs, the processor executes the computer-executable instructions stored in the memory so as to enable the message transmission device to execute the method of the first aspect.

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

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

In a fifth aspect, embodiments of the present application provide a computer storage medium for storing computer software instructions for a first network element, which includes a program designed for the first network element to execute the above aspects.

In a sixth aspect, an embodiment of the present application provides a computer storage medium for storing computer software instructions for a second network element, which includes a program designed for the second network element to execute the above aspects.

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

In an eighth aspect, embodiments of the present application provide a computer program product. The computer program product comprises computer software instructions which are loadable by a processor to cause execution of the procedures described in the method of the first aspect.

In a ninth aspect, an embodiment of the present application provides a chip, which includes a processor, a transceiver component, and optionally a memory, and is configured to execute the message transmission method in the foregoing aspect.

Drawings

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

fig. 2 is a schematic diagram of a network architecture according to an embodiment of the present application;

fig. 3 is a schematic diagram of a network architecture according to 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 illustrating a method for negotiating configuration of a terminal device through NAS messages according to an embodiment of the present application;

fig. 6 is a schematic diagram illustrating another method for negotiating configuration of a terminal device through NAS messages according to an embodiment of the present application;

fig. 7 is a schematic diagram illustrating another method for negotiating configuration of a terminal device through NAS messages according to an embodiment of the present application;

fig. 8 is a schematic diagram of another message transmission method according to an embodiment of the present application;

fig. 9 is a schematic diagram of another message transmission method according to an embodiment of the present application;

fig. 10 is a schematic diagram illustrating another message transmission method according to an embodiment of the present application;

fig. 11 is a schematic diagram of another message transmission method according to an embodiment of the present application;

fig. 12 is a schematic diagram illustrating another message transmission method according to an embodiment of the present application;

fig. 13 is a schematic diagram illustrating another message transmission method 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 now be described in detail with reference to the drawings attached hereto.

The terminal equipment in the application is equipment with a wireless transceiving function, can be deployed on land and comprises an indoor or outdoor, a handheld or a vehicle-mounted terminal; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a User Equipment (UE) or a Customer Premises Equipment (CPE), and may be, for example, a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal, an Augmented Reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and so on.

Fig. 1-3 are schematic diagrams of network architectures applied in the embodiments of the present application. The scenarios shown in fig. 1 to fig. 3 are scenarios in which the terminal device accesses a 3GPP core network or a PSP network from an access network element in an NHN network via a core network of the NHN network. The 3GPP core network shown in fig. 1 is a 4G network, the 3GPP core network shown in fig. 2-3 is a 5G network, wherein in the network architecture shown in fig. 1, the terminal device may further access the PSP network through a Local authentication authorization accounting (PSP AAA) network element of the NHN network from an access network element in the NHN network through a Local authentication authorization accounting (Local AAA Proxy) network element of the NHN network, and the terminal device is taken as the UE in fig. 1-3 for illustration.

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), a third generation partnership project authentication authorization accounting (3rd generation partnership project authorization accounting, 3GPP AAA), a Home Subscription Server (HSS), a service capability opening function (SCEF), a neutral mobility management entity (NH MME), a neutral gateway (NH GW), an interworking gateway (NH gateway), an interworking capability opening function (AAA), a service capability opening function (AAA-AAA), and the like.

In the network architecture shown in fig. 1, the NHN network may interwork with the 4G network through two modes, and in one interworking mode, the NHN network is connected to the 4G network through the ePDG, and the used interfaces include SWa-N, SWn, S2b, SWm, and the like. 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 an S2a-N interface, and the used interface includes STa-N. In addition, the Local AAA Proxy element of the NHN network may also be connected to the PSP AAA element of the PSP network through an AAA interface.

The following is a brief description of the functionality of the network elements involved in the network architecture shown in fig. 1.

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, and may be a base station, for example.

The ePDG is used for establishing an internet protocol security (IPsec) tunnel with the UE when the UE accesses the network through a Non-3GPP (Non-3GPP or N3 GPP).

The PGW has a packet filtering function based on a user, a lawful interception function, an Internet Protocol (IP) address allocation function for interconnection between networks of the UE, a packet transfer level marking in an uplink, charging of an uplink and a downlink service level, control of a service level threshold, control of an uplink and a downlink rate based on a service, and the like.

The 3GPP AAA is used to provide functions such as an authentication authorization message broker.

The HSS is used to store subscriber subscription information and is responsible for storing subscriber-related information, such as subscriber identification, numbering and routing information, security information, location information, Profile information, etc.

The SCEF is a capability open platform in the 4G network, and a third party may call an Application Programming Interface (API) provided by an operator, and subscribe an event to the 3GPP system through the SCEF.

The NH MME, similar to the MME in the 4G network, has main functions of supporting NAS signaling and NAS signaling encryption with the UE, selecting a PGW, allocating a temporary identity to the UE, and providing functions of roaming, tracking, security, and the like.

The NH GW is similar to a PGW and a Serving Gateway (SGW) in a 4G network, and has main functions including a packet filtering function based on a user, a lawful interception function, an IP address allocation function between networks of a UE, a packet transfer level marking in an uplink, charging of an uplink service level and an downlink service level, control of a service level threshold, control of an uplink rate and a downlink rate based on a service, and the like.

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

The IWK-SCEF is a capability open platform in the NHN network, and when the IWK-SCEF is communicated with the 3GPP network, the IWK-SCEF can directly report the subscribed event report to the SCEF in the 3GPP network.

The PSP AAA is used for providing functions of authentication and authorization message agent and the like.

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

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

In the architecture shown in fig. 1, network elements related to the present application mainly include: UE, NH MME, SCEF, IWK-SCEF and HSS.

For the network architectures shown in fig. 2-3, the network architecture diagrams each include a UE, an access network element, an access and mobility management function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), a Unified Data Management (UDM), a User Plane Function (UPF), an authentication server function (AUSF), a network open function (NEF), a neutral access and mobility management function (NH AMF), a neutral deployment session management function (NH), a neutral deployment Session Management Function (SMF), a neutral deployment network function (iw-si), and an iw-network open function (network-function, network-open function (NEF), DN), and the like. The difference between the network architectures shown in fig. 2 and fig. 3 is that in fig. 3, the NHN network and the 5G network are intercommunicated through a non-3GPP Interworking Function (N3 IWF) network element, and the N3IWF network element is similar to an ePDG in the 4G network and is used for establishing 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, and the application is only exemplified with a non-3GPP network access gateway as the N3 IWF.

It should be understood that, while NHN networks are continuously evolving, the next generation NHN network architecture and the interworking architecture of NHN and 5G networks are still under study, and in the future 5G definition, the network architectures shown in fig. 2-3 and the names of the network elements involved in the network architectures may be changed, and the application is only exemplified by the network architectures shown in fig. 2-3 and the network elements involved in the network architectures.

The functions of the network elements involved in the network architectures shown in fig. 2-3 are briefly described below.

The AMF is responsible for access management and mobility management of the terminal device, and in practical application, the AMF includes a mobility management function of an MME in a 4G network and adds the access management function.

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

The UPF is a functional network element of the user plane, and is mainly responsible for connecting an external network, including related functions of the SGW and the PGW of the 4G network, and is mainly responsible for forwarding packet data packets, accounting information, and the like.

The UDM is used to manage subscription information for the user, implementing a backend similar to the HSS in 4G.

The NEF is an open capability platform in the 5G network, and when the NEF is communicated with the NHN network, the NEF can directly report the subscribed event report to the IWK-NEF in the NHN network.

The NH AMF is responsible for access management and mobility management of the terminal device, similar to the AMF in the 5G network.

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

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

The IWK-NEF is an open capability platform in the NHN, and when the IWK-NEF is communicated with the 5G network, the IWK-NEF can directly report the subscribed event report to the NEF in the 5G network.

The DNs are responsible for networks providing services for the terminal devices, for example, some DNs provide internet access functions for the terminal devices, and other DNs provide short message functions for the terminal devices.

In the architectures of fig. 2 to fig. 3, the network elements related to the present application mainly include: UE, NH AMF, UDM, PCF, IWK-NEF, and N3 IWF.

For the network architectures shown in fig. 1 to fig. 3, in the prior art, if a sending end requests to configure a UE, the sending end needs to rely on a specially deployed configuration server to configure the UE, and a configuration process depends on a special channel established between the UE and the configuration server. Specifically, the sending end sends a configuration request to the configuration server through the application layer message, and then forwards the configuration request to the UE through the configuration server. When the networks shown in fig. 1 to fig. 3 are applied to the vertical industries, different configurations may need to be performed for UEs belonging to different vertical industries, and if the above method is used to configure UEs belonging to different vertical industries, different configuration servers need to be deployed for UEs belonging to different vertical industries, and different configuration servers need to establish a special channel with corresponding UEs, which may cause problems of high deployment cost and complex deployment. In addition, in the prior art, the method for sending the configuration request to the UE through the application layer message by the sending end also requires that the UE supports ip protocol stacks (ip traffic threads), that is, the method can only be used for UEs that support ip protocol stacks, and is not applicable to UEs that do not support ip protocol stacks.

The embodiment of the present application provides a message transmission method and apparatus, so as to implement configuration of a terminal device through an NHN network without adding a special configuration server, and the method provided by the present application can configure a terminal device that supports an ip protocol stack and can also configure a terminal device that does not support an ip protocol stack. The method is suitable for the interworking architecture between the NHN network and the 4G network shown in fig. 1, and is also suitable for the interworking architecture between the NHN network and the 5G network shown in fig. 2 to 3.

For convenience of description, the NHN network is referred to as a first network, but the first network is not limited in this application, and may be another non-3GPP network, for example, and the first network is hereinafter described as the NHN network.

The second network in the present application is a network that can enable a sending end to access and can communicate with the first network, and for example, may be a 3GPP network.

The sending end in this application is a device that can request to configure a terminal device, and may be, for example, a server (e.g., 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 is described below with reference to the drawings.

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

s101: the first network element receives a first request from a transmitting 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 that the terminal device be configured according to the configuration parameter. The first network element belongs to a first network, and when the first network is an NHN network, the first network element may be an NH MME or an NH AMF.

In this application, how the first network element receives the first request from the transmitting end is not limited. In a possible implementation manner, referring to S101a-S101b, a first network element receives a first request from a sending end through a second network element, specifically, the second network element receives the first request from the sending end, determines that a terminal device is in a first network according to identification information of the terminal device included in the first request, and sends 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 through the fourth network element, in this implementation manner, after the fourth network element receives the first request from the sending end, it is determined whether the sending end can configure the terminal device, if it is determined that the sending end can configure the terminal device, the fourth network element sends the 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 sends a failure message to the sending end. In the present application, the example that the transmitting end can configure the terminal device is described with reference to S101a1-S101a 3.

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 formed by combining Local AAA Proxy, PSP AAA, IWK-SCEF, and SCEF network elements, and when the second network element belongs to the second network, for example, when the second network element belongs to the 3GPP network, the second network element may be a network element such as HSS, UDM, PCF, and SCEF, and for example, when the second network element belongs to the PSP network, the second network element may be a network element such as PSP AAA, and SCEF.

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

It should be understood that, in the present application, there is no limitation on how the first network element receives the first request from the transmitting end through the second network element. In one possible implementation, the first network element directly receives the first request from the second network element, and in yet another possible implementation, the first network element receives the first request from the second network element through another network element. For example, taking the first network element as an NH AMF network element and the second network element as an UDM network element as an example, the other network elements may be AMF network elements. For another example, taking the first network element as an NH MME and the second network element as an HSS network element as an example, the other network elements may be network elements such as 3GPP AAA and Local AAA Proxy. The following will describe in detail how the first network element receives the first request from the transmitting end through the second network element, and details thereof are not described here.

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

Optionally, after receiving the first request from the sender, the first network element may further send a response message for the first request to the sender, see S101', S101a ', and S101b '. The response message may include acknowledgement information of the first request by the first network element, and may refer to a message acknowledging receipt of the first request or a message acknowledging non-receipt of the first request, for example. In this application, a case where the first network element confirms receipt of the first request is taken as an example for explanation. If the first network element does not receive the first request, it may further request to resend the first request, and so on.

It should be understood that, in this application, the first network element sends the response message for the first request to the sending end, and the response message may be sent through the same path as the path through which the first request from the sending end is received, and details are not described here.

S102: the first network element sends a first request to the terminal device through the NAS message.

In the application, a first request is sent to the terminal device through a first network element in the NHN network, specifically, the first network element 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 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 obtained by modifying an existing NAS message, the first network element may send the NAS message to the terminal device alone, or the NAS message that is being sent to the terminal device at that time may be carried in the NAS message.

It should be understood that, if the first network element receives the first request from the sending end through the second network element and other network elements, when the second network element and other network elements forward the first request from the sending end, the first request may be further analyzed and encapsulated, that is, different messages carrying the first request are sent by the second network element and other network elements, and specific parameters in the first request sent by different network elements may also be different.

In the application, the first request is sent to the terminal device through 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 through the method of the application, that is, the first network element in the first network sends information (such as configuration request, configuration parameters and the like) related to configuration to the terminal devices, and it is not necessary to deploy special configuration servers and establish special channels for the terminal devices belonging to different vertical industries, so that the deployment cost and the deployment complexity can be reduced through the method of the application. In addition, in the application, the first network element sends the first request to the terminal device through the NAS message instead of the application layer message, so the method is not only suitable for the terminal device which supports the ip protocol stack, but also suitable for the terminal device which does not support the ip protocol stack.

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

Optionally, the first response includes one or more of the following information: the confirmation information of the terminal equipment to the first request, the identification information of the terminal equipment, the identification information of the fourth network element, the reference identification information of the fourth network element and the state information of the terminal equipment.

In this application, the confirmation information of the terminal device to the first request refers to a message for confirming the reception of the first request. Of course, in other implementations, the confirmation information may also refer to a message confirming that the first request is not received, in which case, the terminal device may further request to resend the first request, and so on.

In this 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 an SCEF, and for the network architectures shown in fig. 2 to fig. 3, the fourth network element may be an NEF network element.

In this application, the identification information of the fourth network element refers to information that can uniquely identify the fourth network element, and may be, for example, an ID of the fourth network element.

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

In a possible implementation manner, for a first request sent by a sending end, it is necessary for a terminal device to send a state of the terminal device, a state change, or statistical data within a period of time to the sending end, and in this scenario, a first response sent by the terminal device may include identification information of the terminal device, state 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 method and the device do not limit how the first network element sends the first response to the sending end. In one possible implementation, the first network element sends the first response to the sender through the second network element, see S104a-S104b, and in another possible implementation, the first network element sends the first response to the sender through the third network element and the fourth network element, see S105a-S105 c. If the first response is sent to the sending end through the third network element and the fourth network element, the fourth network element may send the first response to the sending end according to the reference ID of the fourth network element.

Wherein the third network element belongs to the first network and the fourth network element belongs to the second network. For example, for the network architectures shown in fig. 1, the third network element may be an IWK-SCEF and the fourth network element may be an SCEF, and for the network architectures shown in fig. 2-3, the third network element may be an IWK-NEF and the fourth network element may be an NEF.

It should be understood that, if the first network element sends the first response to the sending end through the second network element or the third network element and the fourth network element, when the second network element, the third network element and the fourth network element forward the first response from the terminal device, the first response may be further analyzed and encapsulated, that is, different messages carrying the first response are sent by the second network element, the third network element and the fourth network element, and specific parameters in the first responses sent by different network elements may also be different.

It should be appreciated that since the fourth network element belongs to the second network, the identification information of the fourth network element and/or the reference identification information of the fourth network element may be included in the first response, facilitating the first network element to find the fourth network element.

S104 a: the first network element sends a first response to the second network element.

S104 b: and the second network element sends a first response to the sending end.

S105 a: the first network element sends a first response to the third network element.

S105 b: the third network element sends a first response to the fourth network element.

S105 c: and the fourth network element sends the first response to the sending end.

It should be understood that the first network element may select whether to send the first response to the sender in the manner of S104a-S104b or S105a-S105c according to actual requirements.

In this application, if the first network element receives the first request from the sending end through the second network element, before the second network element sends the first request to the first network element, it may also be determined whether the first network supports the configuration requested by the first request, if it is determined that the first network supports the configuration requested by the first request, the first request is sent to the first network element, and if it is determined that the first network does not support the configuration requested by the first request, a failure message is sent to the sending end. In the present application, a case where the first network supports the configuration requested by the first request is taken as an example, refer to S101 c.

In a possible implementation manner, the first network supporting the configuration requested by the first request means that the first network supports configuration types included in the configuration parameters and supports different configuration contents included in each configuration type. For example, if the configuration type requested by the sending end is configuration and configuration update, and the configuration content included in the configuration type is a new service requested to be configured, the configuration requested by the first network to support the first request means whether the first network supports the configuration of the new service.

In this application, before the first network element sends the first request to the terminal device, it may be further determined that the first network supports the configuration requested by the first request, for example, it may be determined that the first network supports the configuration requested by the first request by receiving an authorization indication from the third network element. Wherein the authorization indication indicates 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 means that the first network supports configuration types included in the configuration parameters and supports different configuration contents included in each configuration type; or the configuration requested by the first network to support the first request means that the first network element determines that the first network supports the first request sent from the second network according to the roaming agreement.

In a possible implementation manner, before the first network element receives 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 a sending end of the third network element requests to configure the terminal device according to the configuration parameters, see S102a-S102 b. 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, before the sending end sends the first request to the terminal device through the first network element or through the first network element and the second network element, it may be determined, through the first network element or the second network element, whether the terminal device supports configuring the terminal device through the NAS message.

Optionally, the second network element determines whether the terminal device supports configuring the terminal device through the NAS message, and if it is determined that the terminal device supports configuring the terminal device through the NAS message, the second network element sends the first request to the first network element, and if it is determined that the terminal device does not support configuring the terminal device through the NAS message, the second network element sends the failure message to the sending end. In the present application, a case where the terminal device supports configuration by NAS message is described as an example, refer to S101 d.

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 configuring the terminal device through the NAS message, and if it is determined that the terminal device supports configuring the terminal device through the NAS message, the first network element sends a first request to the terminal device, and if it is determined that the terminal device does not support configuring the terminal device through 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 NAS message is described as an example, refer to S101 d'.

In the present application, the above manners are all implemented on the basis that the first network element determines that the terminal device supports configuring the terminal device through the NAS message, and the terminal device determines that the first network element supports configuring the terminal device through the NAS message.

In this application, for a case that the first network element does not determine whether the terminal device can support configuring the terminal device through the NAS message, and the terminal device does not determine whether the first network element can support configuring the terminal device through the NAS message, the first network element and the terminal device may negotiate to configure the terminal device through the NAS message.

In a possible implementation manner, the determining, by the first network element, that the terminal device supports configuring the terminal device through the NAS message includes: the first network element receives the first indication from the terminal device, and the first network element determines that the terminal device supports configuring the terminal device through the NAS message according to the first indication, see S103 a. The first indication is used for indicating that the terminal equipment supports the configuration of the terminal equipment through the NAS message.

In a possible implementation manner, after the first network element determines that the terminal device supports configuring the terminal device through the NAS message, the method further includes: the first network element sends a second indication to the terminal device, see S103 b. The second indication is used for indicating that the first network supports the terminal equipment configured through the NAS message.

Optionally, the terminal device may send a first instruction to the first network element and receive a second instruction from the first network element in a network discovery process before accessing the first network, and correspondingly, the first network element receives the first instruction from the terminal device and sends the second instruction to the terminal device in the network discovery process before accessing the first network; or, the terminal device sends a first instruction to the first network element and receives a second instruction from the first network element in the authentication process with the first network element, and correspondingly, the first network element receives the first instruction from the terminal device and sends the second instruction to the terminal device in the authentication process with the terminal device; or, the terminal device sends the first instruction to the first network element and receives the second instruction from the first network element in the registration process with the first network element, and correspondingly, the first network element receives the first instruction from the terminal device and sends the second instruction to the terminal device in the registration process with the terminal device.

In the following, with reference to fig. 5 to fig. 7, a process of a first network element negotiating with a terminal device to configure the terminal device through NAS messages in the present application is illustrated.

Referring to fig. 5, a flowchart of a method for negotiating to configure a terminal device through NAS messages according to an embodiment of the present application is shown, where in fig. 5, taking the terminal device as a CPE, the first network as an NHN network, and the second network as a 3GPP network as an example, a process of negotiating to configure the terminal device through NAS messages by the first network element and the terminal device according to the embodiment of the present application 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 through an access network element, where the access network element may be a base station or other equipment.

It should be understood that fig. 5 illustrates an example in which the method for negotiating to configure the terminal device through the NAS message, provided by the embodiment of the present application, is applied to an interworking architecture between the NHN network and the 4G network shown in fig. 1.

The method shown in fig. 5 comprises the following steps:

s201: the access network element broadcasts information to the CPE.

S202: the CPE probes the NHN network and the additional information needed.

S203: the CPE establishes 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 via a NAS message. Optionally, the CPE may carry the first indication in an existing NAS message, or may send the first indication to the NH MME through a new NAS message.

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

Likewise, the NH MME sends the second indication to the CPE via a NAS message. Optionally, the NH MME may carry the second indication to an existing NAS message, or may send the second indication to the CPE through a new NAS message.

It should be understood that the method shown in fig. 5 is that the CPE negotiates to configure the CPE through NAS messages in a 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.

Referring to fig. 6, a flowchart of another method for negotiating to configure a terminal device through NAS messages according to the embodiment of the present application is shown, and a process of negotiating to configure a terminal device through NAS messages by a first network element and a terminal device according to the embodiment of the present application is described in fig. 6, taking the terminal device as a CPE, the first network as an NHN network, and the second network as a 3GPP network as an example. The NH MME network element is an implementation manner of the first network element, the HSS network element is an implementation manner of the second network element, and the CPE accesses the NH MME network element through the access network element, where the access network element may be a base station or other equipment.

It should be understood that fig. 6 illustrates an example in which the method for negotiating to configure the terminal device through the NAS message, provided by the embodiment of the present application, is applied to an interworking architecture between the NHN network and the 4G network shown in fig. 1.

The method shown in fig. 6 comprises the following steps:

s301: and the CPE sends an attachment request carrying the first indication to an access network element.

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

Optionally, after receiving the attach request carrying the first indication sent by the CPE, the NH MME may determine, according to the first indication, that the CPE supports configuring the CPE through the NAS message, and after determining that both the CPE and the NHN network support configuring the CPE through the NAS message, the NH MME may store the information.

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

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

S304: session establishment procedure in NHN network.

S305: and the NH MME sends an attachment acceptance message carrying the second indication to the CPE.

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

In a possible implementation manner, the NH MME sends the attach accept message carrying the second indication to the CPE, and may send the attach accept message to the access network element first, and then the attach accept message is forwarded to the CPE by the access network element.

It should be understood that, if the CPE needs to establish the user plane tunnel to the 3GPP EPS system, the NH MME may also send the first indication to the HSS in the process of establishing the user plane tunnel to the 3GPP EPS system by the CPE. For example, in an interworking mode in which the NHN network is connected to the 4G network through the ePDG, the CPE may carry the first indication in an IKEv2 message to send to the ePDG in the process of establishing the IPSec tunnel with the ePDG, and then the ePDG sends to the HSS via the 3GPP AAA/PSP AAA in a Diameter or Radius message. In the interworking mode in which 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 above S304, when a Session is established between the NH GW and the PGW, the Create Session Request message carries the first indication, and the PGW further sends the first indication to the HSS via the 3GPP AAA/PSP AAA in the Diameter message.

It should be understood that the method shown in fig. 6 is that the CPE negotiates to configure the CPE through NAS messages during authentication or registration of the end device with the first network element.

Referring to fig. 7, a flowchart of another method for negotiating to configure a terminal device through NAS messages according to the embodiment of the present application is shown, and a process of negotiating to configure a terminal device through NAS messages by a first network element and a terminal device according to the embodiment of the present application is described in fig. 7, taking the terminal device as a CPE, the first network as an NHN network, and the second network as a 3GPP network as an example. 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 illustrates an example in which the method for negotiating to configure the terminal device through the NAS message, provided by the embodiment of the present application, is applied to an interworking architecture between the NHN network and the 5G network shown in fig. 2.

The method shown in fig. 7 comprises the following steps:

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

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

In the method shown in fig. 7, after receiving the registration request carrying the first indication, the AMF may send the first indication to the UDM in the following two ways.

In one implementation, 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 a first indication and CPE identification information (e.g., CPE ID), which indicates that the CPE corresponding to the CPE identification information supports configuration through NAS information.

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 may determine that the CPE corresponding to the CPE identification information supports configuration through the NAS message.

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

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

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

S403 a: the AMF sends an AMF registration request message to the UDM.

The AMF registration request message carries a first indication and CPE identification information (e.g., CPE ID), which indicates that the CPE corresponding to the CPE identification information supports configuration via NAS message.

S404 a: the UDM sends an AMF registration response message to the AMF.

Optionally, the AMF registration response message carries 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 acknowledgement information of the AMF for the first indication, which indicates that the NHN network supports configuring the CPE through the NAS message.

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

It should be understood that the method shown in fig. 7 is that the CPE negotiates to configure the CPE through NAS messages during authentication or registration of the end device with the first network element.

The following describes a message transmission method provided in the embodiment of the present application with reference to fig. 8 to fig. 13.

Referring to fig. 8, a flow chart of a message transmission method provided in this embodiment is shown, where in fig. 8, a case where a terminal device is a CPE, a first network is an NHN network, a second network is a 3GPP network, a sending end is a Service Capability Server (SCS)/Application Server (AS), and a second network element belongs to the second network is taken AS an example, a message transmission method provided in this embodiment is described, where an NH MME network element is an implementation manner of the first network element in this embodiment, an HSS network element is an implementation manner of the second network element in this embodiment, an IWK-SCEF network element is an implementation manner of the third network element in this embodiment, and an SCEF network element is an implementation manner of the fourth network element in this embodiment.

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

The method shown in fig. 8 comprises the following steps:

s501: the SCEF receives a first request sent by the SCS/AS.

In the method shown in fig. 8, after the SCEF receives the first request sent by the SCS/AS, it may determine whether the SCS/AS can perform the configuration requested by the first request for the CPE, if the SCEF determines that the SCS/AS cannot perform the configuration requested by the first request for the CPE, send a request failure message to the SCS/AS, where the request failure message may be used to indicate that the SCS/AS cannot perform the configuration requested by the first request for the CPE, and if the SCEF determines that the SCS/AS can perform the configuration requested by the first request for the CPE, send the first request to the HSS. The present application takes the example of the SCEF determining that the SCS/AS can perform the configuration requested by the first request to the CPE AS an example, refer to S502-S503.

S502: the SCEF determines that the SCS/AS may perform the configuration requested by the first request to 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 determining that the NHN network supports the configuration requested by the first request, the HSS performs S505, and if determining that the NHN network does not support the configuration requested by the first request, the HSS sends a failure message to the SCS/AS, where the HSS does not support the configuration requested by the first request, the method is not shown in this application.

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

S505: and the HSS determines that the CPE is in the NHN network according to the identification information of the CPE included in the first request, and then sends the first request to the 3 GPPAAA.

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

S507: local AAA proxy sends a first request to the NH MME.

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

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

In the method shown in fig. 8, taking sending the first request to the NH MME and receiving the response message sent by the NH MME in the re-authentication process initiated by the 3GPP AAA as an example for explanation, in practical application, the first request may also be sent to the NH MME and the response message sent by the NH MME through other processes, which is not limited in the present application.

It should be understood that acknowledgement information of the NH MME to the first request may be included in the response message for the first request, e.g., the acknowledgement message may indicate that the first request is acknowledged.

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

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 this application, the first notification is a notification that the SCS/AS requests to configure the CPE according to the configuration parameters.

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

In this 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 to S514 are optional steps in this application, and the NH MME may directly forward the received first request to the CPE after receiving the first request, or may also forward the received first request to the CPE after performing S513 to S514, which is not limited in this application.

S515: the NH MME sends the first request to the CPE via an NAS message.

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

In the method shown in fig. 8, after the NH MME receives the first response sent by the CPE, the first response may be sent to the SCS/AS in two ways. In one implementation, referring to S517a-S517e, the NH MME sends a first response to the SCS/AS through Local AAA proxy, 3gpp AAA, HSS, and SCEF. In another implementation, referring to S518a-S518c, the NH MME sends a first response to the SCS/AS via IWK-SCEF and SCEF.

In the method shown in fig. 8, the first response includes one or more of the following information: the CPE device may include, but is not limited to, acknowledgement information of the first request by the CPE device, identification information of the CPE device (e.g., CPE ID), identification information of the SCEF (e.g., SCEF ID), reference identification information of the SCEF (e.g., SCEF reference ID), and status information of the CPE device.

In a possible implementation manner, for the first request sent by the SCS/AS, the CPE needs to report its state, a state change, or statistical data within a period of time, in this scenario, the first response sent by the CPE may include the CPEID, the SCEF ID, the SCEF reference ID, and state information of the CPE, and optionally, may further include confirmation information of the CPE on the first request.

Referring to fig. 9, a flowchart of another message transmission method provided in the embodiment of the present application is shown, where in fig. 9, a case where a terminal device is a CPE, a first network is an NHN network, a second network is a 3GPP network, a sending end is an SCS/AS, and a second network belongs to the second network is taken AS an example, and a description is given to the message transmission method provided in the embodiment of the present application, where an NH AMF network element is an implementation manner of the first network element in the embodiment of the present application, a UDM network element or a PCF network element is an implementation manner of the second network element in the embodiment of the present application, an IWK-NEF network element is an implementation manner of the third network element in the embodiment of the present application, and a NEF network element is an implementation manner of the fourth network element in the embodiment of the present application.

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

The method shown in fig. 9 comprises 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 may determine whether the SCS/AS can perform the configuration requested by the first request for the CPE, if the NEF determines that the SCS/AS cannot perform the configuration requested by the first request for the CPE, send a request failure message to the SCS/AS, the request failure message being usable to indicate that the SCS/AS cannot perform the configuration requested by the first request for the CPE, and if the NEF determines that the SCS/AS can perform the configuration requested by the first request for the CPE, send the first request to the UDM or the PCF. The present application takes the case where the NEF determines that the SCS/AS can perform the configuration requested by the first request to the CPE AS an example, see S602, S603, and S603 a.

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

S603: the NEF sends a 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 determines that the CPE is in the NHN network according to the identification information of the CPE included in the first request, S604 is performed.

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

It should be understood that the AMF is registered for the CPE in the method shown in fig. 9.

S603 a: 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 determines that the CPE is in the NHN network according to the identification information of the CPE included in the first request, then S604a is executed.

S604 a: the PCF sends a first request to the AMF.

It should be understood that S603-S604 and S603a-S604a may only select one way to proceed in a network, and the user may decide which way to deploy based on the configuration.

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

In the method shown in fig. 9, the AMF may query the NHAMF of the current NHN network according to the NH AMF when the CPE registers.

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, unlike the first response in this application, may include acknowledgement information of the first request by the AMF, for example, the acknowledgement message may indicate that the first request is acknowledged.

It should be understood that, corresponding to the two methods of sending the first request to the AMF in S603-S604 and S603a-S604a, the AMF in fig. 9 may reply to the NEF in two ways, one way of replying to the response is shown in S607-S608, and the other way of replying to the response is shown in S607a-S608 a.

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 the first request is sent in S603-S604.

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

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

It should be understood that the manner of replying to the response in S607a-S608a corresponds to the manner of sending the first request in S603a-S604 a.

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.

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

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

S612: the NH AMF sends the first request to the CPE via a 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 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 new NAS message, the NH MME may send the NAS message to the CPE alone, 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 a first response to the first request sent by the CPE over the NAS message.

In the method shown in fig. 9, after the NH AMF receives the first response sent by the CPE, the first response may be sent to the SCS/AS in three ways. In one implementation, see S614a-S614d, NH AMF sends a first response to SCS/AS via AMF, UDM, and NEF, in another implementation, see S615a-S615d, NH AMF sends a first response to SCS/AS via AMF, PCF, and NEF, and in yet another implementation, see S616a-S616c, NH AMF sends a first response to SCS/AS via IWK-NEF, and NEF.

In the method shown in fig. 9, the first response includes one or more of the following information: confirmation information of the CPE to the first request, a CPE ID, identification information of the NEF (e.g., NEF ID), reference identification information of the NEF (e.g., NEFreference 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 state, a state change, or statistical data within a period of time, in this scenario, the first response sent by the CPE may include the CPEID, the NEF ID, the NEF reference ID, and state information of the CPE, and optionally, may further include confirmation information of the CPE on the first request.

In this embodiment of the present application, the method shown in fig. 9 may also be applied 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 an N3IWF, the NAS message in S612-S613 is encapsulated by an IKEv2 message or transmitted on an IPSec channel, and the interaction steps between the NH AMF and the AMF in fig. 9 are that S605, S606, S614a, and S615a are forwarded via Local AAA proxy and N3 IWF.

In the embodiments of the present application, the above description is to implement configuration of a terminal device through interworking between an NHN network and a 3GPP network. In a possible implementation manner, the sending end may directly configure the terminal device through the 3GPP network without resorting to the NHN network. For example, in the method shown in fig. 9, taking a 3GPP network as a 5G network as an example for explanation, if a sending end directly configures a terminal device through the 5G network, in the method shown in fig. 9, NH AMF is AMF in the 5G network, which is equivalent to that no interaction exists between NH AMF and an AMF network element, and optionally, an IWK SCEF network element exists only in a roaming scenario.

Referring to fig. 10, a flowchart of another message transmission method provided in the embodiment of the present application is shown, where in fig. 10, a case where a terminal device is a CPE, a first network is an NHN network, a second network is a PSP network, a sending end is an SCS/AS, and a second network element belongs to the second network is taken AS an example, and the message transmission method provided in the embodiment of the present application is described.

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

The method shown in fig. 10 comprises the following steps:

s701: the SCEF receives a 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 on the CPE, if the SCEF determines that the SCS/AS cannot perform the configuration requested by the first request on the CPE, send a request failure message to the SCS/AS, where the request failure message may be used to indicate that the SCS/AS cannot perform the configuration requested by the first request on the CPE, and if the SCEF determines that the SCS/AS can perform the configuration requested by the first request on the CPE, send the first request to the PSP AAA. For the example of the SCEF determining that the SCS/AS can perform the configuration requested by the first request to the CPE, refer to S702-S703.

S702: the SCEF determines that the SCS/AS may perform the configuration requested by the first request to the CPE.

S703: the SCEF sends a 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 determines that the CPE is in the NHN network according to the identification information of the CPE included in the first request, S705 is performed.

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 NHMME through the Local AAA proxy, that is, the PSP AAA sends the first request to the Local AAA proxy, and the Local AAAproxy forwards the first request to the NH MME.

Optionally, when the PSP AAA sends the first request to the NH MME, a third indication may be carried, 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 for the first request to the PSP AAA.

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 this application, and the response message may include acknowledgement information of the AMF for the first request, for example, the acknowledgement message may indicate that the first request is acknowledged.

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 PSPAAA through the Local AAA proxy, that is, the NH MME sends the first request to the Local AAA proxy, and then the Local AAAproxy forwards the first request to the PSP AAA.

In the method shown in fig. 10, it is described by taking an example that, in a re-authentication process initiated by the PSP AAA, the first request is carried in a message sent by the re-authentication process to send the first request to the NH MME, and a response message sent by the NH MME is received, in practical application, the PSP AAA may also send the first request to the NH MME through a message in another communication process, and receive a response message sent by the NHMME, and of course, the first request may also be sent to the NHMME as a new message without using an existing communication flow, which is not limited in this application.

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

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.

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

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

S711: the NH MME sends the first request to the CPE via an NAS message.

S712: the NH MME receives a first response sent by the CPE through the NAS message and aiming at the first request.

In the method shown in fig. 10, after the NH MME receives the first response sent by the CPE, the NH MME may further send the first response to the SCS/AS. Alternatively, the first response may be sent to the SCS/AS in two ways. In one implementation, 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, referring to S714a-S714c, the NH MME sends a first response to the SCS/AS via IWK-SCEF and SCEF.

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 PSP AAA and Local AAA proxy are independent network elements, the first response in S713a may be sent to PSP AAA through Local AAAproxy, further sent to SCEF by PSP AAA, and sent to SCS/AS through SCEF.

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

It should be understood that the network elements IWK-SCEF, Local AAA proxy, PSP AAA and SCEF may be jointly or separately arranged in one or more devices, and when the IWK-SCEF, Local AAA proxy, PSP AAA and SCEF network elements are jointly arranged in one device, the interaction between them may be considered as an internal operation, that is, the step of jointly arranging between the network elements of one device may be omitted, and in this case, the IWK-SCEF, Local AAA proxy, PSP AAA and SCEF network elements jointly arranged in one device may be equivalent to the second network element in this application. Certainly, 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 jointly arranged in one device, and at this time, the first network element and the second network element are the same device and are both devices formed by jointly arranging the NH MME, the IWK-SCEF, the Local AAA proxy, the PSP AAA and the SCEF network element.

In this embodiment of the application, the method shown in fig. 10 may also be applied to the network architecture shown in fig. 2, and when the method shown in fig. 10 is applied to the network architecture shown in fig. 2, the network element NH MME in fig. 10 is replaced by NH AMF, the IWK-SCEF is replaced by IWK-NEF, and the SCEF is replaced by NEF, referring to fig. 11, in fig. 11, S801 to S814c perform the same operations as S701 to S714c in fig. 10, respectively, and are not described again.

Referring to fig. 12, a flowchart of another message transmission method provided in the embodiment of the present application is shown, and the message transmission method provided in the embodiment of the present application is described in fig. 12 by taking an example in which the terminal device is a CPE, the first network is an NHN network, the second network is a 3GPP network or a PSP network, the sending end is an SCS/AS, and the second network element belongs 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 of applying the message transmission method provided in the embodiment of the present application to an interworking architecture between an NHN network and a 4G network, or an interworking architecture between an NHN network and a PSP network. When applied to an interworking architecture between an NHN network and a 4G network, the HSS network element shown in fig. 12 corresponds to the HSS network element shown in fig. 12, and when applied to an interworking architecture between an NHN network and a PSP network, the PSP AAA network element shown in fig. 12 corresponds to the PSP AAA network element shown in fig. 12.

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

The method shown in fig. 12 comprises the following steps:

s901: the SCEF receives a 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, if the SCEF determines that the SCS/AS cannot perform the configuration requested by the first request for the CPE, send a request failure message to the SCS/AS, where the request failure message may be used to indicate that the SCS/AS cannot perform the configuration requested by the first request for the CPE, and if the SCEF determines that the SCS/AS can perform the configuration requested by the first request for the CPE, send the first request to the HSS/PSP AAA. The present application takes the example of the SCEF determining that the SCS/AS can perform the configuration requested by the first request to the CPE AS an example, see S902-S903.

S902: the SCEF determines that the SCS/AS may perform the configuration requested by the first request to 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 the first request to the HSS/PSP AAA in the subscription process, optionally, a message carried in the first request in the subscription process may be sent to the HSS/PSP AAA, or may be sent in other processes, or may send to the HSS/PSP AAA separately 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, if it is determined that the NHN network does not support the configuration requested by the first request, the HSS/PSP AAA may carry a request failure message in the response message sent to the SCEF, and if it is determined that the NHN network supports the configuration requested by the first request, the HSS/PSP AAA may carry a request acknowledgement in the response message sent to the SCEF, and may also carry NHN network information where the CPE currently locates, for example, the NHN network information where the CPE currently locates may include an identifier of an IWK-SCEF of the NHN network where the CPE currently locates, an identifier of an NH MME, an identifier of the NHN network where the CPE currently locates, or the like.

After the SCEF receives the response message to 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 NHN network where the CPE is currently located may be determined according to the information of the NHN network where the CPE is currently located, and S906 is performed.

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

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

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

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 acknowledgement information of the first request by the NH MME, for example, the acknowledgement 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 the first request to the CPE via an NAS message.

S912: the NH MME receives a first response sent by the CPE through the NAS message and aiming at the first request.

In the method shown in fig. 12, after the NH MME receives the first response sent by the CPE, the first response may be sent to the SCS/AS in the same manner AS in fig. 8-11. FIG. 12 shows only two of these implementations, see S913a-S913c and S914a-S914 c.

In this embodiment of the present application, the method shown in fig. 12 may also be applied to the network architecture shown in fig. 2, and when the method shown in fig. 12 is applied to the network architecture shown in fig. 2, the network element NH MME in fig. 12 is replaced by NH AMF, the IWK-SCEF is replaced by IWK-NEF, the SCEF is replaced by NEF, and the HSS is replaced by UDM/PSP AAA, as shown in fig. 13, S1001 to S1014c perform the same operations as S901 to S914c in fig. 12, which are not described again.

The above-mentioned scheme provided by the present application is mainly introduced from the perspective of interaction between network elements. It is to be understood that each network element described above, in order to implement the above functions, includes a corresponding hardware structure and/or software module for performing each function. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software, with the exemplary elements and algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the case of using an integrated unit, fig. 14 shows a possible exemplary block diagram of an apparatus involved in the embodiment of the present invention, where the apparatus 1400 may exist in the form of software, or may exist in the form of a terminal device or a first network element or a second network element, or may be a chip in the terminal device or a chip in the first network element or a chip in the second network element. The apparatus 1400 comprises: a processing unit 1402 and a communication unit 1403. The processing unit 1402 is configured to control and manage actions of the apparatus 1400, for example, when the apparatus 1400 is a terminal device, the processing unit 1402 is configured to execute a technical process such as determining a first response according to the first request, when the apparatus 1400 is a first network element, the processing unit 1402 is configured to execute the technical process such as S101d' in fig. 4 by carrying the first request in an NAS message, and when the apparatus 1400 is a second network element, the processing unit 1402 is configured to execute the technical process such as S101c and S101d in fig. 4. A communication unit 1403 is used to support communication of the apparatus 1400 with other network entities. The communication unit 1403 may be configured to support the apparatus 1400 to perform technical processes of S102, S103a, S103b, and the like in fig. 4 when the apparatus 1400 is a terminal device, the communication unit 1403 may be configured to support the apparatus 1400 to perform technical processes of S102, S103a, S103b, S101b, S101a ', S102a, S102b, S104a, and S105a, and the like in fig. 4 when the apparatus 1400 is a first network element, and the communication unit 1403 may be configured to support the apparatus 1400 to perform technical processes of S101a, S103a3, S101b, S101a ', S101b ', and S104b, and the like in fig. 4 when the apparatus 1400 is a second network element. The apparatus 1400 may also include a storage unit 1401 for storing program codes and data for the apparatus 1400.

The processing unit 1402 may be a processor or a controller, such as a general Central Processing Unit (CPU), a general purpose processor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication unit 1403 may be a communication interface, a transceiver, a transceiving 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 device 1400 according to the embodiment of the present invention may be the device shown in fig. 15.

Fig. 15 is a schematic diagram of a possible logical structure of the apparatus according to the foregoing embodiments, provided for an embodiment of the present application. As shown in fig. 15, the apparatus 1500 may include at least one processor 1501. In the embodiment of the present application, the processor 1501 is configured to control and manage the actions of the apparatus, and optionally, the apparatus may further include a memory 1502 and a transceiver 1503. The processor 1501, transceiver 1503 and memory 1502 may be interconnected or interconnected by a bus 1504. The memory 1502 is used for storing codes and data of the device. The transceiver 1503 is used to support the device for communication.

The following describes the respective constituent elements of the apparatus in detail:

the processor 1501 is a control center of the apparatus, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 1501 is a CPU, or may be implemented as an ASIC, or as one or more integrated circuits configured to implement embodiments of the present invention, such as: one or more DSPs, or one or more FPGAs.

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

The Memory 1502 may be, but is not limited to, 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 of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a compact disc Read-Only Memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 1502, which may be separate, is coupled to the processor 1501 via a communication bus 1504. Memory 1502 may also be integrated with processor 1501.

The transceiver 1503, which may be any transceiver or the like, is used for communication with other nodes, such as: a first network element, etc. And may also be used to communicate with communications Networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc. 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 Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 15, but this is not intended to represent only one bus or type of bus.

The configuration of the apparatus shown in fig. 15 does not constitute a limitation of the device and may include more or fewer components than those shown, or some of the components may be combined, or a different arrangement of components.

When the apparatus shown in fig. 15 is a terminal device or a chip in a terminal device, the following steps may also be performed:

in a possible implementation manner, the transceiver 1503 is configured to receive a first request from a first network element, where the first request is a request from a transmitting end, the first request includes configuration parameters, and the first request is used to request that the apparatus is configured according to the configuration parameters; a processor 1501 configured to determine a first response according to the first request; the transceiver 1503 is further configured to send the first response to the first network element through a non-access stratum, NAS, message, where the first network element belongs to a first network.

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

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

before receiving a first request sent by a 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 through a NAS message.

after sending the first indication to the first network element, receiving a second indication from the first network element, the second indication indicating that the first network supports configuring the apparatus by a NAS message.

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

in a network discovery process before accessing the first network, sending the first indication to the first network element, and receiving the second indication from the first network element; or, in the authentication process with the first network element, sending the first indication to the first network element, and receiving the second indication from the first network element; or, in a registration process with the first network element, sending the first indication to the first network element, and receiving 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.

Embodiments of the present application further provide a computer storage medium for storing computer software instructions for the message transmission apparatus shown in fig. 14 and 15, which includes program codes designed to execute the method embodiments. The transmission of the message can be effected by executing the stored program code.

The embodiment of the application also provides a computer program product. The computer program product comprises computer software instructions which can be loaded by a processor for implementing the method in the above-described method embodiments.

An embodiment of the present application further provides a chip, where the chip includes a processor and a transceiver component, and optionally further includes a storage unit, and is configured to execute the method according to the foregoing embodiment of the present application.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The various illustrative logical units and circuits described in this application may be implemented or operated upon by design of 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 thereof. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., 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.

The steps of a method or algorithm described in the embodiments herein may be embodied directly in hardware, in a software element executed by a processor, or in a combination of the two. The software cells may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may be disposed in a terminal device. In the alternative, the processor and the storage medium may reside as discrete components in a terminal device.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While the invention has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the invention. Accordingly, the specification and figures are merely exemplary of the invention as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the invention. It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method for message transmission, comprising:

a first network element receives a first request from a sending end, wherein the first request comprises configuration parameters, the first request is used for requesting to configure terminal equipment according to the configuration parameters, and the first network element belongs to a first network;

and the first network element sends the first request to the terminal equipment through a non-access stratum (NAS) message.

2. The method of claim 1, wherein after the first network element sends the first request to the terminal device via a NAS message, the method further comprises:

the first network element receives a first response to the first request from the terminal device.

3. The method of claim 2, further comprising:

the first network element sends the first response to the sending end through a third network element and a fourth network element, wherein the third network element belongs to the first network, and the fourth network element belongs to the second network; or,

and the first network element sends the first response to the sending end through a second network element, wherein the second network element belongs to the first network or the second network.

4. A method according to claim 2 or 3, wherein the first response includes one or more of the following information: the terminal device confirms the first request, the identification information of the terminal device, the identification information of the fourth network element, the reference identification information of the fourth network element and the state information of the terminal device.

5. 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 comprises:

the first network element receives an authorization indication from a third network element, the authorization indication indicating that the first network supports the configuration requested by the first request.

6. The method according to any of claims 1 to 5, wherein the first network element receives a first request from a transmitting end, comprising:

the first network element receives the first request through a second network element.

7. The method according to any of claims 1 to 6, wherein before the first network element sends the first request to the terminal device, further comprising:

and the first network element determines that the terminal equipment supports the configuration of the terminal equipment through NAS information.

8. The method of claim 7, wherein the determining, by the first network element, that the terminal device supports configuring the terminal device through a NAS message comprises:

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 through an NAS message;

and the first network element determines that the terminal equipment supports the configuration of the terminal equipment through NAS information according to the first indication.

9. The method of claim 8, wherein after determining that the terminal device supports configuring the terminal device via NAS messaging, the method further comprises:

and the first network element sends a second indication to the terminal equipment, wherein the second indication is used for indicating that the first network supports the configuration of the terminal equipment through NAS information.

10. The method of claim 9, further comprising:

the first network element receives the first indication from the terminal device and sends the second indication to the terminal device in a network discovery process before the terminal device accesses the first network; or,

the first network element receives the first indication from the terminal equipment and sends the second indication to the terminal equipment in the authentication process with the terminal equipment; or,

and the first network element receives the first indication from the terminal equipment and sends the second indication to the terminal equipment in the registration process with the terminal equipment.

11. The method according to any 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.

12. A method for message transmission, comprising:

a second network element receives a first request from a sending end, wherein the first request comprises configuration parameters and identification information of terminal equipment, and the first request is used for requesting to configure the terminal equipment according to the configuration parameters;

and the second network element determines that the terminal equipment is in a first network according to the identification information of the terminal equipment, and then sends the first request to the first network element, wherein the first network element belongs to the first network.

13. The method of claim 12, wherein the second network element belongs to the first network or belongs to a second network.

14. The method of claim 13, wherein the second network element belongs to the first network;

the first request further includes a third indication indicating that the first request is from the first network.

15. The method according to any of claims 12 to 14, wherein before the second network element sends the first request to the first network element, further comprising:

the second network element determines that the first network supports the configuration requested by the first request.

16. The method of claim 15, wherein the configuration parameters include at least one configuration type, the configuration type including configuration and configuration updates, software firmware management, status and performance monitoring, and diagnostics, each configuration type including different configuration content;

the second network element determining that the first network supports the configuration requested by the first request, comprising:

the second network element determines that the first network supports the at least one configuration type and supports different configuration contents included in each configuration type.

17. The method according to any of claims 12 to 16, wherein before the second network element sends the first request to the first network element, further comprising:

and the second network element determines that the terminal equipment supports the configuration of the terminal equipment through a non-access stratum (NAS) message.

18. The method according to any of claims 12 to 17, wherein after the second network element sends the first request to the first network element, further comprising:

and the second network element receives a first response from the first network element and sends the first response to the sending end, wherein the first response is a response which is sent by the terminal equipment to the first network element and aims at the first request.

19. The method of claim 18, wherein the first response includes one or more of the following information: the terminal device confirms the first request, the identification information of the terminal device, the identification information of a fourth network element, the reference identification information of the fourth network element and the state information of the terminal device, wherein the fourth network element belongs to the second network.

20. The method according to any of the 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.

21. A method for message transmission, comprising:

a terminal device receives a first request from a sending end through a first network element, wherein the first request comprises configuration parameters, the first request is used for requesting to configure the terminal device according to the configuration parameters, and the first network element belongs to a first network;

and the terminal equipment sends a first response aiming at the first request to the first network element through a non-access stratum (NAS) message.

22. The method of claim 21, wherein the first response includes one or more of the following information: the terminal device confirms the first request, the identification information of the terminal device, the identification information of the fourth network element, the reference identification information of the fourth network element and the state information of the terminal device, wherein the fourth network element belongs to the second network.

23. The method of claim 21 or 22, wherein before the terminal device receives the first request from the transmitting end through the first network element, the method further comprises:

and the terminal equipment sends a first indication to the first network element, wherein the first indication is used for indicating that the terminal equipment supports the configuration of the terminal equipment through NAS information.

24. The method of claim 23, wherein after the terminal device sends the first indication to the first network element, the method further comprises:

and the terminal equipment receives a second indication from the first network element, wherein the second indication is used for indicating that the first network supports the configuration of the terminal equipment through NAS information.

25. The method of claim 24, further comprising:

the terminal device sends the first indication to the first network element and receives the second indication from the first network element in the process of network discovery before accessing the first network; or,

the terminal equipment sends the first instruction to the first network element and receives the second instruction from the first network element in the authentication process with the first network element; or,

and the terminal equipment sends the first indication to the first network element and receives the second indication from the first network element in the registration process with the first network element.

26. The method according to any of the 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.

27. A message transmission device comprising a transceiver, a memory and a processor;

the transceiver is used for the device to communicate;

the memory for storing a computer program;

the processor is configured to call and run the computer program from the memory, so that the apparatus executes the message transmission method according to any one of claims 1 to 11.

28. A message transmission device comprising a transceiver, a memory and a processor;

the transceiver is used for the device to communicate;

the memory for storing a computer program;

the processor is configured to call and run the computer program from the memory, so that the apparatus executes the message transmission method according to any one of claims 12 to 20.

29. A message transmission device comprising a transceiver, a memory and a processor;

the transceiver is used for the device to communicate;

the memory for storing a computer program;

the processor is configured to call and run the computer program from the memory, so that the apparatus executes the message transmission method according to any one of claims 21 to 26.

30. A terminal device, characterized in that it comprises the apparatus of claim 29.