WO2019154048A1

WO2019154048A1 - Nb-iot network communication method, apparatus, and storage medium

Info

Publication number: WO2019154048A1
Application number: PCT/CN2019/072495
Authority: WO
Inventors: 常红娜; 徐蓓
Original assignee: 华为技术有限公司
Priority date: 2018-02-09
Filing date: 2019-01-21
Publication date: 2019-08-15
Also published as: CN110139264B; CN110139264A

Abstract

The embodiments of the present application provide an NB-IoT network communication method, an apparatus, and a storage medium, for implementing communication between a terminal device and a service platform in a scenario where a plurality of service platforms are subscribed. In the embodiments of the present application, a first network device receives a first request comprising the identifier of a terminal device, determines a target service platform from N service platforms subscribed by the terminal device, and sends a first response, wherein at least two service platforms of the N service platforms correspond to the same APN, said N is an integer greater than 1, and the first response is used to instruct a connection to be established between the terminal device and the target service platform, such that communication between the terminal device and the service platform may be implemented in the scenario where the terminal device has a plurality of service platforms subscribed thereto.

Description

Communication method, device and storage medium of NB-IoT network

This application claims priority to Chinese Patent Application No. 201,810, 134, 288, 288, filed on February 9, 2018, and entitled "Communication Method, Apparatus, and Storage Medium for NB-IoT Network". The entire contents are incorporated herein by reference.

Technical field

The present application relates to the field of communications, and in particular, to a communication method, apparatus, and storage medium for an NB-IoT network.

Background technique

The Internet has evolved from a human-centric network to the Internet of Things. In a human-centric network, humans generate and consume information, while the Internet of Things sends and receives and processes information between distributed components such as objects. The rapid development of the Internet of Things (IoT) has brought enormous challenges to the Evolved Packet System (EPS) defined by the 3rd Generation Partnership Project (3GPP). In the Internet of Things, there is a typical narrow bandwidth Internet of Things (NB-IoT) that is widely used. In NB-IoT, the terminal device is usually idle most of the time, the amount of data transmitted per day is extremely low, and a certain transmission delay (for example, smart water meter) is allowed. Secondly, a large number of terminal devices in the Internet of Things are in a static state for a long time and do not move frequently with time. Third, the connection between terminal devices in the Internet of Things is different from the connection between “people”. The traffic model of the Internet of Things is no longer the following behavior. It may be the main behavior. The terminal devices in the Internet of Things usually go to the service platform. Report some data.

A terminal device in NB-IoT usually needs to report data to a service platform. In this case, when the manufacturer leaves the terminal devices in the Internet of Things, the IP address of the service platform is usually burned to the terminal device. In this case, the terminal device can send data to the service platform according to the IP address of the service platform that is programmed to itself.

With the advancement of smart cities, the functions of terminal devices in the Internet of Things have evolved from single to multiple, so that one terminal device may need to communicate with multiple service platforms. Currently, a communication scheme of NB-IoT network is needed. The communication between the terminal device and the service platform in the scenario of signing multiple service platforms is implemented.

Summary of the invention

The embodiment of the present invention provides a communication method, device, and storage medium for a NB-IoT network, which are used to implement communication between a terminal device and a service platform in a scenario of signing multiple service platforms.

In a first aspect, the embodiment of the present application provides a communication method of a NB-IoT network, where the first network device receives a first request, where the first request includes an identifier of the terminal device, and the first network device signs the subscription from the terminal device. Among the N service platforms, the target service platform is determined, and at least two service platforms exist in the N service platforms, and the access point names APN corresponding to at least two service platforms are the same, and N is an integer greater than 1; the first network device sends a first response; wherein the first response is used to indicate that a connection is established between the terminal device and the target service platform. Since there are at least two service platforms in the N service platforms, and the APNs corresponding to the at least two service platforms are the same, the terminal device may send a message through a connection established between the terminal device and the target service platform, so that the terminal can be at the terminal. The device communicates with the service platform in the scenario of signing multiple service platforms.

In a possible implementation, the first network device determines the target service platform from the N service platforms subscribed by the terminal device, including any one of the following: if the first request includes the identifier of the service platform, and The service platform is a service platform that is contracted with the terminal device, and the first network device determines the service platform as the target service platform; if the first request includes the identifier of the service platform, and the service platform is not a service platform that is contracted with the terminal device, the first The network device determines the preset service platform corresponding to the terminal device as the target service platform, and the preset service platform is one of the N service platforms; if the first request does not include the identifier of the service platform, the first network device uses the terminal The preset service platform corresponding to the device is determined as the target service platform. In this way, the flexibility of the solution can be improved. Even if the identifier of the legal service platform is not included in the first request, the first network device can determine a legal target service platform for the terminal device, thereby ensuring the terminal device and the target service platform. The communication between the two is normal.

In a possible implementation, after receiving the first request, the method further includes: if the identifier of the service platform is not included in the first request, the first network device sends a second response to the terminal device; wherein the second response is used Indicates that no connection is established between the terminal device and the target service platform. Or, if the first request includes the identifier of the service platform and the service platform is not the service platform that is contracted with the terminal device, the first network device sends a third response to the terminal device, where the third response is used to indicate the terminal device and the target service. The connection is not established between the platforms; or the third response is used to indicate that no connection is established between the terminal device and the target service platform, and the service platform is not a service platform that is contracted with the terminal device. In this way, the terminal device can clearly establish the cause of the connection failure, thereby improving the success rate of the next connection.

In a possible implementation, after the first network device determines the target service platform from the N service platforms that are subscribed by the terminal device, before the sending the first response, the first network device further includes: sending, by the first network device, the second network device And the first network device sends the first response, and the first network device sends the first response after receiving the success response for creating the connection. In this way, the specific situation of the connection establishment of the terminal can be notified, so that the terminal device can perform subsequent data transmission.

In order to improve the flexibility of the solution, in a possible implementation, if the first network device is the MME network element and the second network device is the SCEF network element, the connection success response is created between the MME network element and the SCEF network element. Sent after the control plane connection is established. In another possible implementation manner, if the first network device is a MME network element, and the second network device is a P-GW network element, creating a connection success response is to establish a group between the terminal device and the P-GW network element. The data network is sent after the PDN connection.

In a second aspect, the embodiment of the present application provides a communication method of a NB-IoT network, where the second network device receives a create connection request sent by the first network device, where the connection request is a first network device slave terminal. After the target service platform is determined by the N service platforms that are signed by the device, at least two service platforms exist in the N service platforms, and at least two service platforms have the same access point name APN; N is greater than 1. An integer; after determining that the terminal device establishes a connection with the target service platform, the second network device sends a create connection success response to the first network device. In this way, the terminal device can send a message through the connection established between the terminal device and the target service platform, so that the communication between the terminal device and the service platform can be implemented in the scenario where the terminal device signs the multiple service platforms.

In order to improve the flexibility of the solution, in a possible implementation, if the first network device is an MME network element and the second network device is a SCEF network element, the second network device determines between the terminal device and the target service platform. After the connection is established, the connection establishment success response is sent to the first network device, and the SCEF network element sends a connection establishment success response to the first network device after establishing a control plane connection between the MME network element and the SCEF network element. In another possible implementation manner, if the first network device is a mobility management module MME network element, and the second network device is a P-GW network element, the second network device determines the terminal device and the target service platform. After the connection is established, the connection establishment success response is sent to the first network device, and the P-GW network element sends a connection establishment success response to the first network device after the PDN connection is established between the terminal device and the P-GW network element.

In a possible implementation, after the second network device receives the create connection request sent by the first network device, before sending the connection connection success response to the first network device, the method further includes: if the target service platform is not configured with the terminal device and the target a preset parameter corresponding to the connection between the service platforms, the second network device sends a configuration request to the target service platform, where the configuration request is used to trigger the target service platform to configure the preset parameter; the second network device determines the terminal device and After the connection between the target service platforms is established, the connection establishment success response is sent to the first network device, where the second network device sends a connection establishment success response to the first network device if the target service platform is configured with the preset parameters. It can be seen that the configuration of the preset parameters is also detected during the process of creating the connection, so that the reliability of data transmission between the subsequent terminal and the target service platform can be improved.

In a possible implementation, after the second network device receives the create connection request sent by the first network device, the method further includes: if the target service platform does not configure a preset parameter corresponding to the connection between the terminal device and the target service platform, Then: the second network device sends a fourth response, where the fourth response is used to indicate that no connection is established between the terminal device and the target service platform; or the fourth response is used to indicate that the terminal device and the target service platform are not connected. And the target service platform does not have preset parameters configured. In this way, the terminal device can clearly establish the cause of the connection failure, thereby improving the success rate of the next connection.

In a possible implementation, the first request includes a disaster tolerance flag bit, where the disaster tolerance flag is used to indicate whether to enable a disaster tolerance mechanism for the target service platform; the target service platform corresponds to the primary server and the standby server; After the network device determines that the connection between the terminal device and the target service platform is established, and after the connection response is successfully sent to the first network device, the second network device further determines that the target service platform needs to be opened according to the disaster tolerance flag. In the disaster recovery mechanism, the link corresponding to the target service platform is monitored; if the link corresponding to the primary server is in a fault state, and the link corresponding to the standby server is in a non-fault state, the link corresponding to the standby server is activated, and Sending the mobile originating MO message sent by the terminal device to the standby server corresponding to the target service platform; if the link corresponding to the primary server is in a non-fault state, the link corresponding to the primary server is activated, and the standby server is corresponding. The link is deactivated, and the MO message sent by the received terminal device is sent to the target service platform. Primary server. Combined with the application disaster recovery mechanism, the reliability of data transmission between the subsequent terminal and the target service platform can be improved.

In a possible implementation, after determining that the terminal device establishes a connection with the target service platform, the second network device sends a connection connection success response to the first network device, and further includes: the second network device receiving the terminal device sending And modifying the bearer request, where the modify bearer request includes the service platform to be updated; the second network device sends a modify bearer response, where the modify bearer response is used to indicate that the terminal device establishes a connection with the service platform to be updated. In this way, it is possible to lay the foundation for the terminal device to switch between service platforms.

In order to be compatible with the prior art, in a possible implementation, sending the first response includes: if the terminal device transmits the MO message through the RDS protocol, the second network device carries the port number of the target service platform in the first response. The second network device sends the first response.

In a third aspect, the embodiment of the present application provides a communication method of a NB-IoT network, where the terminal device sends a first request, where the first request includes an identifier of the terminal device, and the terminal device receives the first response. The first response is that the first network device determines the target service platform from the N service platforms subscribed by the terminal device, and determines that the connection between the terminal device and the target service platform is established; the first response is used to indicate the terminal device and A connection is established between the target service platforms; at least two service platforms exist in the N service platforms, and at least two service platforms have the same access point name APN; N is an integer greater than 1. The terminal device can send a message through the connection established between the terminal device and the target service platform, so that communication between the terminal device and the service platform can be implemented in the scenario where the terminal device signs the multiple service platforms.

In a possible implementation, the first request includes an identifier of the service platform. If the service platform is a service platform that is contracted with the terminal device, the service platform is the target service platform; if the service platform is not contracted with the terminal device, The service platform, the default service platform corresponding to the terminal device is the target service platform, and the preset service platform is one of the N service platforms; the first request does not include the identifier of the service platform, and the preset service corresponding to the terminal device The platform is the target service platform. In this way, the flexibility of the solution can be improved. Even if the identifier of the legal service platform is not included in the first request, the first network device can determine a legal target service platform for the terminal device, thereby ensuring the terminal device and the target service platform. The communication between the two is normal.

In a possible implementation, the identifier of the service platform is not included in the first request; or the first request includes the identifier of the service platform and the service platform is not the service platform that is contracted with the terminal device; then the terminal device sends the first request. Afterwards, the method further includes: receiving, by the terminal device, the second response or the third response; wherein the second response is used to indicate that the connection between the terminal device and the target service platform is not established; and the third response is used to indicate between the terminal device and the target service platform The connection is not established; or the third response is used to indicate that no connection is established between the terminal device and the target service platform, and the service platform is not a service platform that is contracted with the terminal device. In this way, the terminal device can clearly establish the cause of the connection failure, thereby improving the success rate of the next connection.

In a possible implementation, after the sending the first request, the method further includes: receiving, by the terminal device, the fourth response; wherein the fourth response is that the network device determines that the target service platform does not configure the connection between the terminal device and the target service platform. And sending, in the case of the corresponding preset parameter, where the fourth response is used to indicate that no connection is established between the terminal device and the target service platform; or the fourth response is used to indicate that no connection is established between the terminal device and the target service platform. And the target service platform does not have preset parameters configured. In this way, the terminal device can clearly establish the cause of the connection failure, thereby improving the success rate of the next connection.

In a possible implementation, after the sending the first response, the method further includes: the terminal device sends a modify bearer request, where the modify bearer request includes a service platform to be updated; and the terminal device receives the modify bearer response, where the bearer response is modified. Establishing a connection between the terminal device and the service platform to be updated. In this way, it is possible to lay the foundation for the terminal device to switch between service platforms.

In order to be compatible with the prior art, in a possible implementation, the first response includes a port number of the target service platform; after receiving the first response, the terminal device further includes: the terminal device sends the mobile to the first network device by using the RDS protocol. The originating MO message; wherein the MO message includes the port number of the target service platform.

In a fourth aspect, an embodiment of the present application provides a network device, where the network device includes a memory, a transceiver, and a processor. The transceiver includes a transmitter and a receiver. Wherein: the memory is used to store the instruction; the processor is configured to control the transceiver to perform signal reception and signal transmission according to the instruction for executing the memory storage, and the network device is configured to perform the first aspect or the foregoing when the processor executes the instruction stored in the memory Any one of the methods.

In a fifth aspect, an embodiment of the present application provides a network device, where the network device includes a memory, a transceiver, and a processor. The transceiver includes a transmitter and a receiver. Wherein: the memory is used to store the instruction; the processor is configured to control the transceiver to perform signal reception and signal transmission according to the instruction for executing the memory storage, and the network device is configured to perform the second aspect or the foregoing when the processor executes the instruction stored in the memory Any of the two methods.

In a sixth aspect, an embodiment of the present application provides a terminal device, where the terminal device includes a memory, a transceiver, and a processor. The transceiver includes a transmitter and a receiver. Wherein: the memory is used to store the instruction; the processor is configured to execute the instruction stored in the memory, and control the transceiver to perform signal reception and signal transmission, and when the processor executes the instruction stored in the memory, the terminal device is configured to execute the third aspect or the foregoing Any of the three methods.

In a seventh aspect, the embodiment of the present application provides a network device, which is used to implement any one of the foregoing first aspect or the first aspect, and includes a corresponding functional module, which is used to implement the steps in the foregoing method.

The eighth aspect, the embodiment of the present application provides a network device, which is used to implement the method of any one of the foregoing second aspect or the second aspect, including a corresponding function module, which is used to implement the steps in the foregoing method.

The ninth aspect, the embodiment of the present application provides a terminal device, which is used to implement any one of the foregoing third or third aspects, including a corresponding functional module, which is used to implement the steps in the foregoing method.

According to a tenth aspect, the embodiment of the present application provides a computer storage medium, where the computer storage medium stores instructions, when executed on a computer, causing the computer to perform any of the first aspect to the third aspect or any aspect thereof. The method in the possible implementation.

In an eleventh aspect, the embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform any of the first aspect to the third aspect or any possible implementation of any aspect. The method in .

DRAWINGS

1 is a schematic structural diagram of a communication system to which an embodiment of the present application is applied;

2 is a schematic flowchart of a communication method of an NB-IoT network according to an embodiment of the present application;

FIG. 3 is a schematic diagram of another communication method of an NB-IoT network according to an embodiment of the present disclosure;

4 is a schematic flowchart of a communication method of another NB-IoT network according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of a communication method of another NB-IoT network according to an embodiment of the present disclosure;

FIG. 6 is a schematic flowchart of a communication method of another NB-IoT network according to an embodiment of the present disclosure;

FIG. 7 is a schematic flowchart of a communication method of another NB-IoT network according to an embodiment of the present disclosure;

FIG. 8 is a schematic flowchart of a communication method of another NB-IoT network according to an embodiment of the present application;

FIG. 9 is a schematic flowchart of a communication method of another NB-IoT network according to an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure;

FIG. 13 is a schematic structural diagram of another network device according to an embodiment of the present disclosure;

FIG. 14 is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

FIG. 15 is a schematic structural diagram of another terminal device according to an embodiment of the present disclosure.

Detailed ways

FIG. 1 exemplarily shows a schematic diagram of a communication system architecture applicable to an embodiment of the present application. The communication system architecture is a communication system architecture of an NB-IoT network. As shown in FIG. 1 , the communication system includes a terminal device 101 and a wireless device. Resident Radio Access Network (RAN) 102, Home Subscriber Server (HSS) network element 103, Mobility Management Entity (MME) network element 104, Service Capability (Service Capability) The Exposure Function (SCEF) network element 105, the Serving Gateway (S-GW) network element 106, the Packet Data Network Gateway (P-GW) network element 107, and the service platform set 108.

As shown in FIG. 1, for control plane function optimization, after uplink data is transmitted from the RAN 102 to the MME network element 104, the transmission path is divided into two branches: one branch is transmitted to the P-GW network through the S-GW network element 106. The element 107 is then transmitted to the service platform, and the other branch is transmitted to the service platform via the SCEF network element 105. Branches transmitted to the service platform through the SCEF network element 105 can transmit non-network protocol (IP) data. The downlink data transmission path transmitted by the service platform to the terminal device is the same, and only the transmission direction is reversed. For user plane function optimization, the transmission path of the uplink data and the downlink data is “terminal device 101--RAN102--S-GW network element 106--P-GW network element 107--service platform”. IP data and non-IP data can be transmitted on this path.

The SCEF network element 105 shown in FIG. 1 is introduced to support non-IP data transmission of a narrow bandwidth IoT terminal, and may also be referred to as a capability open platform. The communication system can establish a connection dedicated to transmitting non-IP data between the MME network element and the SCEF network element. The HSS network element in FIG. 1 may be a permanent storage location of user subscription data, and is located in the home network to which the user subscribes. For example, the HSS network element can store information about the service platform signed by the terminal device.

One or more service platforms may be included in the service platform set 108 shown in FIG. 1, such as the service platform 111, the service platform 112, and the service platform 113 shown in FIG. The Access Point Name (APN) corresponding to any two service platforms in the service platform set 108 may be the same or different, for example, the APN 109 corresponding to the service platform 111 and the service platform 112. The service platform 113 corresponds to the APN 110. The APN corresponding to each service platform may be pre-allocated, for example, the operator may allocate the service platform. The second network device (such as a SCEF network element or a P-GW network element) can also adjust the APN allocated by the service platform. For example, the service platform can be calculated according to the identifier of the terminal device and the identifier of the service platform, and certain rules. The APN, that is, the APN allocated by a service platform can be fixed or flexible. Optionally, the second network device (such as a SCEF network element or a P-GW network element) may also save the correspondence between the APN and the service platform. The APN can be deployed by the operator. For example, the APN 109 can be an IP Multimedia Subsystem (IMS), and the APN 110 can be the Internet (English can be written as the Internet). The terminal device 101 in FIG. 1 can communicate with multiple service platforms included in the service platform set 108. For example, the terminal device can report a message to the service platform 111 or report the message to the service platform 113. The terminal device in Fig. 1 may be a device such as a water meter and a gas meter.

Based on the above, FIG. 2 exemplarily shows a schematic flowchart of a communication method of an NB-IoT network provided by an embodiment of the present application. As shown in FIG. 2, the method includes:

Step 2101: The terminal device sends a first request, where the first network device receives the first request, where the first request includes the identifier of the terminal device.

Step 2102: The first network device determines the target service platform from the N service platforms that are subscribed by the terminal device, where there are at least two service platforms in the N service platforms, and the access point names corresponding to the at least two service platforms are the same, N Is an integer greater than 1. The first network device may be the MME network element 104 of FIG. In some cases, the first network device in this step may also be the S-GW network element 106, the P-GW network element 107 or the SCEF network element 105, and the like. The identifier of the service platform of the N service platforms that the terminal device subscribes to (the service platform may also be referred to as a Service Capability Server (SCS). The identifier of the service platform may be written as an SCS identifier; the service platform may also be referred to as an application server. The application server (AS) can be stored in the HSS network element 103 shown in FIG. 1. The identifier of the service platform can be the domain name of the service platform, the IP address of the service platform, or the uniform resource identifier of the service platform. Uniform Resource Identifier (URI). In another optional implementation manner, the identifier of the service platform of the N service platforms that the terminal device subscribes to may be sent by the terminal device to the first network device, for example, the identifier of the service platform of the N service platforms that the terminal device subscribes to may be Carry in the first request.

After the step 2101, if the first network device is the MME network element, after the MME network element receives the first request, the MME network element can obtain the user subscription data from the HSS network element, for example, the MME network element sends the HSS network element to the HSS network element. Obtaining a user subscription data request, and receiving a user subscription data response fed back by the HSS network element, where the user subscription data response includes an identifier of the service platform signed by the terminal device.

After the first network device determines that the connection between the terminal device and the target service platform is established, the following step 2103 can be performed.

Step 2103: The first network device sends a first response, and the terminal device receives the first response. The first response is that the first network device determines the target service platform from the N service platforms that the terminal device subscribes to, and determines the terminal device and The connection is sent after the connection between the target service platforms; the first response is used to indicate that the terminal device establishes a connection with the target service platform.

The first request may be an attach request or a Packet Data Network (PDN) connection request, the attach request English may be written as an attach request, the attach request may also be referred to as a location update request, and the PDN connection request in English may be written as PDN connectivity. Request. If the first request is an attach request (also referred to as a location update request), the first response is an attach success response (which may also be referred to as a location update reception or a location update response); if the first request is a PDN connection request, then A response can establish a successful response for the PDN connection.

After the foregoing step 2102, before the step 2103, an optional implementation manner is further provided, where the first network device sends a create connection request to the second network device, and the second network device receives the create connection request sent by the first network device. Wherein, the creation of the connection request is sent by the first network device after determining the target service platform from the N service platforms subscribed by the terminal device. After determining that the terminal device establishes a connection with the target service platform, the second network device sends a create connection success response to the first network device. The first network device receives the create connection success response fed back by the second network device. The first network device sends a first response after receiving the success response for creating a connection.

In order to improve the flexibility of the solution, the embodiment of the present application provides a solution for establishing a connection between the terminal and the target service platform. In an optional implementation manner, if the first network device is the MME network element, the second network device is the SCEF. The network element, after the SCEF network element establishes a control plane connection between the MME network element and the SCEF network element, sends a connection connection success response to the first network device, that is, the connection success response is the MME network element and the SCEF network element. Sent after establishing a control plane connection. In this case, the connection between the terminal and the target service platform includes three parts of the connection channel, which are respectively a connection channel between the terminal and the MME network element, and a control plane connection channel between the MME network element and the SCEF network element. And the connection channel between the SCEF network element and the target service platform.

In another optional implementation manner, if the first network device is an MME network element, and the second network device is a packet data network gateway P-GW network element, the P-GW network element is in the terminal device and the P-GW network. After the packet data network PDN connection is established between the elements, a connection connection success response is sent to the first network device, that is, the connection success response is sent after the terminal device establishes a PDN connection with the P-GW network element. In this case, the connection between the terminal and the target service platform includes two parts of the connection channel, which is a PDN connection channel between the terminal and the P-GE (also referred to as a user between the terminal and the P-GE). Surface connection channel) and the connection channel between the SCEF network element and the target service platform.

After establishing the connection between the terminal device and the target service platform, the terminal device may transmit a message through a connection between the terminal device and the target service platform, and the transmitted message may be referred to as a mobile originated (MO) message. In the embodiment of the present application, the MO message is a general term for messages sent by the terminal device.

In the embodiment of the present application, N may be a positive integer. When N is 1, it indicates that the terminal device only signs one service platform, and the only service platform signed by the terminal device is the target service platform.

When N is an integer greater than 1, there may be two application scenarios. In the first application scenario, the two APNs corresponding to any two of the N service platforms are different, and it can be said that there is no APN corresponding to multiple service platforms in the N service platforms, and one APN corresponds to A service platform. Optionally, FIG. 3 is a schematic diagram showing another communication method of the NB-IoT network provided by the embodiment of the present application. As shown in FIG. 3, the terminal device 3101 is served by the service platform 3105 and the service platform 3106. The platform 3105 allocates the APN3107, and the service platform 3106 allocates the APN3108. The APN3107 and the APN3108 are two different APNs. For example, the APN3107 can be an IMS, and the APN3108 can be an Internet. In the scenario shown in FIG. 3, the terminal device needs to report the message to multiple service platforms, but the two APNs allocated by the two service platforms corresponding to the terminal device are different, that is, the terminal device corresponds to multiple APNs, and each APN is used. Correspond to a service platform. In this case, the corresponding connection can be established for different APNs. For example, the second network device 3102 can establish the connection 3103 and the connection 3104 of the terminal device 3101, the connection 3103 corresponds to the APN3107, and the connection 3104 corresponds to the APN3108. The channel sends a message, and the second network device can forward the message transmitted by the different channel to the corresponding platform. The second network device 3102 in FIG. 3 may be a SCEF network element. In this case, the related control plane connection established by the connection between the terminal device and the target service platform is the MME network element 104--SCEF network element in FIG. 105--service platform; or the second network device 3102 in FIG. 3 may be a P-GW network element, in which case the relevant user plane connection established by the connection between the terminal device and the target service platform is the above FIG. MME network element 104--S-GW network element 106--P-GW network element 107--service platform; For example, if the terminal device 3101 needs to send a message to the service platform 3105, the message can be sent through the connection 3103, and the second network device 3102 forwards the message received through the connection 3103 to the service platform 3105. For another example, if the terminal device 3101 needs to send a message to the service platform 3106, the message can be sent over the connection 3104, and the second network device 3102 forwards the message received through the connection 3104 to the service platform 3106. The connection in the embodiment of the present application may also be referred to as a channel, such as a channel between the terminal and the target service platform.

In the first application scenario, the implementation shown in FIG. 3 may be applied, and the solution shown in FIG. 2 may be applied to establish a connection between the terminal device and the target service platform. The solution shown in FIG. 2 can not only implement the case where one APN corresponds to one service platform in the first application scenario, but also applies to the case where one APN corresponds to multiple service platforms.

When N is an integer greater than 1, in the second application scenario, at least two service platforms exist in the N service platforms, and the APNs corresponding to at least two service platforms are the same. In this application scenario, at least one first APN exists in all APNs corresponding to the terminal device, and one of the first APNs corresponds to at least two service platforms. In this application scenario, at least one second APN may also exist. A second APN corresponds to at least one service platform. The second application scenario may be the application scenario shown in FIG. 1 above. The service platform 111 and the service platform 112 corresponding to the terminal device 101 correspond to the same APN 109, and the APN 110 corresponds to only one service platform 113. In FIG. 1, APN 110 may also correspond to multiple service platforms. In this scenario, the device can save resources and reduce the management difficulty of the APN to reduce the number of configured APNs. When multiple service platforms correspond to one ANP, the terminal device and target can be implemented by using the solution provided in Figure 2 above. Communication between service platforms.

FIG. 4 exemplarily shows a schematic flowchart of a communication method of another NB-IoT network provided by an embodiment of the present application. As shown in FIG. 4, after step 2103 of FIG. 2 above, step 2104 to step 2106 may be performed.

In step 2104, the terminal device sends an MO message through the channel corresponding to the established connection (which may also be described as being connected to the corresponding bearer). The MO message includes the identifier of the terminal device.

In an optional implementation manner, if the first network device is the MME network element and the second network device is the SCEF network element, the MO message is first sent to the MME network element by using the connection between the terminal device and the MME network element, and then Then, the MME network element sends a connection to the SCEF network element through a control plane connection between the MME network element and the SCEF network element.

In another optional implementation manner, if the first network device is the MME network element and the second network device is the P-GW network element, the MO message may be connected through the user plane between the terminal device and the P-GW network element. (or called PDN connection) is sent to the P-GW network element.

Step 2105: The second network device determines, according to the MO message, a target service platform corresponding to the connection corresponding to the terminal device. In an optional implementation manner, the second network device may store a correspondence between the connection corresponding to the terminal device and the target service platform, and after the second network device receives the MO message by connecting the corresponding channel, the connection may be determined to be corresponding to the connection. The target service platform, and then forwards the received MO message to the target service platform. Optionally, the second network device may store a correspondence between the connection and the target service platform in an Evolved Packet System (EPS) bearer table (the English of the bearer table may be written as a bearer context).

Step 2106: The second network device sends the MO message to the target service platform.

After the above step 2101, the first network device may perform the

above steps

2102 and 2103. Optionally, after the foregoing step 2101, the network device may not perform step 2102 and step 2103, that is, the first network device does not determine the target service platform, and sends a response to the terminal device indicating that the connection is not established.

In the above step 2102, the first network device determines that the target service platform may be multiple, and the first network device that determines the target service platform may be the MME network element. In this case, the first network device and the second network. Devices can be different network elements. In some cases, the first network device may be another network element, such as a SCEF network element or a P-GW network element. In this case, the first network device may be the same network element as the second network device. FIG. 5 is a schematic flowchart diagram showing another communication method of another NB-IoT network according to an embodiment of the present application. In FIG. 5, an example is taken to determine that a first network device of a target service platform is an MME network element. As shown in FIG. 5, after step 2101, the following scheme can be performed:

Step 4001: Whether the identifier of the service platform is included in the first request, if the identifier of the service platform is included, step 4201 is performed; if the identifier of the service platform is not included, step 4101 is performed or step 4102 is performed.

In step 4201, the identifier of the service platform included in the first request is legal. If it is legal, step 4301 is performed; if not, step 4102 is performed or step 4103 is performed. Optionally, determining whether the identifier of the service platform included in the first request is legal has a plurality of manners, for example, determining whether the identifier of the service platform included in the first request is a service platform among the N service platforms that the terminal device subscribes to, Legal means that the service platform identified by the identifier of the service platform included in the first request is a service platform that is contracted with the terminal device; the illegal means that the service platform identified by the identifier of the service platform included in the first request is not The service platform signed by the terminal device. Optionally, the first network device obtains the identifiers of the N service platforms that are subscribed by the terminal device in multiple manners, such as the foregoing manner of obtaining from the HSS network element.

Step 4301: The first network device may determine, as the target service platform, the service platform identified by the identifier of the service platform included in the first request.

Step 4102: The first network device determines the preset service platform corresponding to the terminal device as the target service platform. Optionally, the preset service platform corresponding to the terminal device is a service platform in the N service platforms that are contracted with the terminal device. Optionally, the preset service platform may be set in advance, or may be N Any service platform in the contracted service platform may also be a service platform selected from N contracted service platforms according to certain rules.

Step 4101: The first network device generates a second response, and sends a second response to the terminal device. The second response is used to indicate that the terminal device does not establish a connection with the target service platform.

Step 4103: The first network device generates a third response, and sends a third response to the terminal device. The third response is used to indicate that the terminal device does not establish a connection with the target service platform. Alternatively, the third response is used to indicate that the terminal device does not establish a connection with the target service platform, and may also indicate that the service platform identified by the identifier of the service platform included in the first request is not a service platform that is contracted with the terminal device.

In the scheme shown in FIG. 5, since the terminal device indicates that the terminal device does not establish a connection with the target service platform by the second response or the third response, the terminal device may transmit the request again for requesting establishment of the connection. Further, if the third response is used to indicate that the terminal device does not establish a connection with the target service platform, and may also indicate that the service platform identified by the identifier of the service platform included in the first request is not a service platform that is contracted with the terminal device, Let the terminal device know the reason why the connection is not established, and lay the foundation for the subsequent establishment of the connection again.

After the step 2102, the second network device may further check the preset parameters corresponding to the connection between the terminal device and the target service platform. If the preset parameters are not configured, the target service may be triggered to perform the preset parameters. The configuration may also feed back the response of the connection establishment failure to the terminal device. If the preset parameters are not configured successfully, the MO message transmission of the subsequent terminal device fails to be transmitted. In the embodiment of the present application, the configuration of the preset parameters is checked in the process of establishing the connection, so that the subsequent terminal can be guaranteed. The higher success rate of the MO message sent by the device, and also the service transmission is not interrupted, thereby reducing the power consumption of the terminal device and reducing the message transmission delay.

FIG. 6 and FIG. 7 are each a schematic diagram showing a flow of a communication method of another NB-IoT network provided by an embodiment of the present application. In FIG. 6, the first network device that performs the foregoing step 2102 is an MME network element. For example, an example is given in which the second network device is a SCEF network element as an example. That is to say, in FIG. 6, the transmission path of the message of the terminal device and the target service platform is the path of the MME network element-SCEF network element-target service platform in FIG. The path shown in Figure 6 can be used to transmit NON-IP messages (NON-IP messages can also be referred to as non-IP messages) and can also be used to transport IP messages.

In FIG. 7 , an example in which the first network device performing the foregoing step 2102 is the MME network element is taken as an example, and the second network device is a P-GW network element as an example. That is to say, in FIG. 7, the transmission path of the message of the terminal device and the target service platform is the path of the MME network element-S-GW network element-P-GW network element--target service platform in FIG. It can be known to those skilled in the art that FIG. 6 and FIG. 7 are only two examples. In FIG. 6, any one of steps 5102 to 5107 performed by the SCEF network element may also be performed by other network devices, such as P. - GW network element execution; in FIG. 7, any of steps 6102 to 6107 and 6102 to 7001 performed by the P-GW network element may also be performed by other network devices, such as by a SCEF network element. The path shown in Figure 7 can be used to transport IP messages.

The embodiments of the present application are described below with reference to FIG. 6 and FIG. 7. As shown in FIG. 6, step 5101 is performed after step 2102.

Step 5101: The MME network element sends a create connection request to the SCEF network element, and the English for creating the connection request may be written as a create PDN connection request. The identity of the target service platform can be included in the create connection request.

Step 5102: Determine whether the target service platform configures a preset parameter corresponding to the connection between the terminal device and the target service platform. If yes, execute step 5106. If not, execute step 5103; the preset parameter may be a parameter in the NIDD configuration message. NIDD configuration parameters such as message may include any of the following or any more: for example, an external identifier (External Identifier), International Mobile Subscriber Integrated Services Digital Network identifier (Mobile Subscriber International ISDN / PSTN number , MSISDN), service The identifier of the platform (the service platform identifier can be written as SCS identifier or AS identifier ), the T8Transaction Reference ID ( TTRI), and the non-IP data delivery duration (Non-IP Data Delivery, NIDD Duration). T8 Interface destination address (T8 destination address), T8 interfaces long-term transaction reference ID (T8 long Term transaction reference ID , TLTRI), requested operation (requested Action), PDN connection setup options (PDN connection establishment option). The target service platform needs to go to the SCEF network element to set the identity of the target service platform, the T8 interface, the T8 interface, the T8 interface, the terminal device identifier (the terminal device identifier can be written as the UE identifier), and the SCEF network element. The connection can be associated with the user external identifier and the target service platform to facilitate the conversion and routing of the user identification. For example, after the SCEF network element associates the information together, the internal identification of the terminal device (such as international mobile user identification) can be The identifier (International Mobile Subscriber Identification Number, IMSISDN, etc.) is converted into an external identifier of the terminal device (such as the IP address, URL, etc. of the terminal device), and the target service platform corresponding to the external identifier of the terminal device is determined, thereby The message sent by the device is sent to the corresponding target service platform.

Step 5103: The SCEF network element sends a configuration request to the target service platform, where the configuration request is used to trigger the target service platform configuration preset parameter; after the target service platform receives the configuration request 5103, step 5104 is performed.

Step 5104: The target service platform configures a preset parameter corresponding to the connection between the terminal device and the target service platform; and after the configuration succeeds the preset parameter, step 5105 is performed.

Step 5105: The target service platform sends a configuration response to the SCEF network element to indicate that the preset parameter configuration is successful. The SCEF network element performs step 5106 after receiving the configuration response indicating that the preset parameter configuration is successful. Optionally, the SCEF network element may also receive a response indicating that the preset parameter configuration fails. If the SCEF network element receives the response indicating that the preset parameter configuration fails, the SCEF network element may feed back the connection establishment to the terminal device. A failed response.

Optionally, the preset parameter may be NIDD. In this case, the configuration request in step 5103 may be an NIDD configuration initialization message, and the English may be written as NIDD Configuration Initial. The NIDD configuration initialization message may trigger the target service platform to complete the NIDD configuration. . The configuration response in step 5105 can be an NIDD configuration response, and the English can be written as an NIDD Configuration Request.

Step 5106: The SCEF network element stores the correspondence between the connection and the target service platform, and then performs step 5107. There are various ways to associate the storage connection with the target service platform. For example, the identifier of the target service platform can be stored in the EPS bearer table.

Step 5107, the SCEF network element sends a connection connection success response to the MME network element; afterwards, step 2103 is performed;

Step 2103: The MME network element sends a first response to the terminal device. That is, the first network device sends the first response if the target service platform is configured with preset parameters.

As shown in FIG. 7, step 6101 is performed after step 2102.

Step 6101: The MME network element sends a connection establishment request to the P-GW network element, and the English for creating the connection request may be written as a create PDN connection request. The identity of the target service platform can be included in the create connection request.

Step 6102: Determine whether the target service platform is configured with a preset parameter corresponding to the connection between the terminal device and the target service platform, and if yes, execute step 6106. If not, execute step 7001; preset corresponding to the connection between the terminal device and the target service platform The parameters can be tunnel parameters, the address of the target service platform.

Step 6106: The P-GW network element stores the correspondence between the connection and the target service platform, and then performs step 6107. There are various ways to associate the storage connection with the target service platform. For example, the identifier of the target service platform can be stored in the EPS bearer table.

Step 6107: The P-GW network element sends a create connection success response to the MME network element; and then step 2103 is performed.

In step 7001, the P-GW network element sends a fourth response. Optionally, the P-GW network element may first send a fourth response to the MME network element, and then the MME network element sends a fourth response to the terminal device. The terminal device receives the fourth response, where the fourth response is sent if the target service platform does not configure the preset parameter corresponding to the connection between the terminal device and the target service platform.

The fourth response is used to indicate that the terminal device does not establish a connection with the target service platform. Alternatively, the fourth response is used to indicate that the terminal device is not connected to the target service platform, and the target service platform is not configured with the preset parameters. In this way, the terminal device can explicitly connect the cause of the connection failure, thereby laying the foundation for the subsequent successful connection establishment.

In the embodiment of the present application, a service platform may have a primary server and a standby server, thereby implementing an active/standby disaster recovery mechanism. FIG. 8 is a schematic flowchart diagram showing another communication method of the NB-IoT network provided by the embodiment of the present application. As shown in FIG. 8, the second network device can monitor the working status of the primary server and the standby server of the service platform. When you need to send information to the service platform, you can use the link with normal working status to send. The monitoring of the primary server and the standby server of the service platform may be performed by a SCEF network element or a P-GW network element. For example, if the transmission path between the terminal device and the target service platform is to be transmitted to the target service platform through the SCEF network element through the MME network element, the SCEF network element can monitor the target service platform; if the terminal device and the target service platform The transmission path between the MME and the P-GW is transmitted to the target service platform through the S-GW network element and the P-GW network element. The target service platform can be monitored by the P-GW network element. In FIG. 8 , the second network device is used as an example of a SCEF network element or a P-GW network element. Optionally, the monitoring of the same service platform may also be performed by the SCEF network element and the P-GW network element simultaneously. get on. In FIG. 8, steps 7101 to 7105 may be performed after the above step 2103. It can also be performed after the above step 2102.

As shown in FIG. 8 , in step 7101, the second network device detects the link corresponding to the target service platform, if the link corresponding to the primary server of the second network device to the target service platform is in a fault state, and the second network device arrives If the link corresponding to the standby server of the target service platform is in a non-fault state, step 7102 is performed. If the link corresponding to the primary server of the target network platform is in a non-fault state, step 7103 is performed, that is, Optionally, if the link corresponding to the primary server of the target network platform is in a non-fault state, and the link corresponding to the standby server is in a fault state or a non-fault state, step 7103 is performed. Optionally, detecting, by the second network device, the link of the target server platform may be implemented by sending a heartbeat packet. For example, the second network device periodically sends a heartbeat packet to the primary server of the target service platform.

Step 7102: The second network device may detect the heartbeat packet of the link corresponding to the standby server according to the local configuration or the DNS query to the IP address of the standby server, and determine the link corresponding to the standby server according to the heartbeat packet of the link corresponding to the standby server. If the link corresponding to the standby server is in a non-fault state, the link corresponding to the standby server is activated. Therefore, the MO message sent by the subsequently received terminal device can be sent to the standby server corresponding to the target service platform.

Step 7103: Activate the link corresponding to the primary server, and deactivate the link corresponding to the standby server. Therefore, the MO message sent by the received terminal device can be sent to the primary server corresponding to the target service platform. Deactivating a link in the embodiment of the present application means that the link is in an inactive state, that is, an unavailable state.

In the above step 7101, optionally, when the second network device determines to enable the disaster tolerance mechanism for the target service platform, the second network device initiates detection of the link corresponding to the target service platform. In an optional implementation manner, in the foregoing step 2101, the first request may carry a disaster tolerance flag, and the disaster tolerance flag is used to indicate whether to enable a disaster tolerance mechanism for the target service platform. For example, setting the location of the DR flag to 1 indicates that the DR mechanism is enabled. The location of the DR flag indicates that the connection does not enable the DR mechanism. The second network device can determine whether to enable the disaster recovery mechanism of the target service platform according to the disaster tolerance flag.

In another optional implementation manner, if the first request carries the disaster tolerance flag, and the information on the disaster tolerance flag indicates that the disaster tolerance mechanism is enabled, the second network device may determine the terminal device from the data subscribed by the terminal device. Whether to sign a disaster recovery mechanism. If the terminal device does not sign the disaster recovery mechanism, the second network device (such as the MME network element) may feed back the connection setup failure response to the terminal device, and may optionally feed back the connection failure to the terminal device because the terminal device does not sign the disaster tolerance. mechanism.

If the terminal device has been contracted to the disaster recovery mechanism, the disaster recovery flag indicating that the disaster recovery mechanism is enabled may be carried in the creation connection request in step 5101 or step 6101, and the SCEF network element or the P-GW network element receives the creation. When the connection request is carried out, and the disaster tolerance flag is carried in the indication that the disaster recovery mechanism is enabled, the disaster recovery mechanism for the target service platform is determined to be started, so that the link detection function for the target service platform is started, that is, the above step 7101 is performed.

In another optional implementation manner, the disaster recovery initiation policy may be configured on the second network device, for example, the association between the terminal device and the disaster recovery startup policy, or the association between the service platform and the disaster recovery startup policy. The disaster recovery startup policy can include starting the disaster recovery mechanism or not starting the disaster recovery mechanism. Optionally, the disaster recovery startup policy may include under what conditions the disaster recovery mechanism is started, and the like. If the second network device determines to enable the disaster tolerance mechanism for the target service platform according to the disaster recovery initiation policy corresponding to the terminal identifier or the target service platform identifier, the link of the target service platform is detected.

Through the embodiment shown in FIG. 8 , the active/standby disaster recovery scenario can be implemented in the embodiment of the present application. Even if one server of the target service platform fails, the service of the terminal device to the target service platform can be ensured without interruption, which can be reduced. The retransmission of the terminal device can reduce the power consumption of the terminal device, and the terminal device does not perceive the switching between the primary server and the standby server.

In the embodiment of the present application, the Reliable Data Service (RDS) protocol can be compatible. The RDS protocol can be applied to the transmission path of the MME network element-SCEF network element. The SCEF network element can obtain the port number of the target service platform by parsing the RDS message header, so that the message sent by the terminal device is correctly forwarded to the target service platform.

Optionally, if the second network device determines that the terminal device is to enable the RDS mechanism, that is, if the terminal device transmits the MO message through the RDS protocol, the port number of the target service platform is carried in the first response; and the first response is sent. After receiving the first response, the terminal device sends the MO message to the second network device by using the RDS protocol, where the MO message includes the port number of the target service platform.

Optionally, it may be determined between the foregoing step 2101 and the insufficient 2103 whether the terminal device needs to enable the RDS mechanism. Or, between steps 5101 to 5107 of FIG. 6, the SCEF network element performs a step of determining whether the terminal device wants to enable the RDS mechanism. Optionally, if the SCEF network element determines that the terminal device needs to enable the RDS mechanism, the port connection number of the target service platform may be carried in the create connection success response sent in step 5107 of FIG. 6 above, and optionally the RDS enable flag may also be carried. . Optionally, the MME network element carries the port number and the RSD enable flag of the target service platform carried in the connection success response in the first response of step 2103. The port number of the target service platform and the RSD enable flag can also be transmitted to the terminal device through other messages. The RDS enable flag is used to instruct the terminal device to transmit the MO message through the RDS protocol.

FIG. 9 exemplarily shows a schematic flowchart of a communication method of another NB-IoT network provided by an embodiment of the present application. As shown in FIG. 9, steps 7201 to 7203 of the method may be performed after the foregoing step 2103. The method includes:

Step 7201: The terminal device sends a modify bearer request to the MME network element, and the MME network element sends the modify bearer request to the second network device, where the second network device receives the modify bearer request sent by the terminal device. The second network device may be a SCEF network element or a P-GW network element. The modified bearer request includes the service platform to be updated; the English for modifying the bearer request may be written as a modify bearer request.

Step 7202: The SCEF network element or the P-GW network element establishes a connection between the terminal device and the service platform to be updated. Optionally, the correspondence between the SCEF network element or the P-GW network element storage terminal device and the service platform to be updated, such as the storage terminal device, the identifier of the service platform to be updated, and the establishment between the terminal device and the service platform to be updated. The connection between the three is connected. Optionally, the SCEF network element or the P-GW network element may update the identifier of the service platform corresponding to the terminal device in the EPS bearer table, for example, modify the identifier of the service platform corresponding to the terminal device in the EPS bearer table from the identifier of the target service platform. The identifier of the service platform to be updated.

In step 7203, the SCEF network element or the P-GW network element may send a modified bearer response to the terminal device (for example, the MME network element may send a modified bearer response to the terminal device). The terminal device receives the modified bearer response. The modify bearer response is used to indicate that the terminal device establishes a connection with the service platform to be updated. Modifying the English of the bearer response can be written as a modify bearer response. After step 7203, the terminal device may continue to send the MO message to the service platform to be updated.

Based on the foregoing content and the same concept, the present application provides a network device for performing any one of the first network device side in the foregoing methods shown in FIG. 2 to FIG. FIG. 10 is a schematic structural diagram of a network device provided by the present application. As shown in FIG. 10, the network device 7301 includes a processor 7303, a transmitter 7302, a receiver 7307, and a memory 7305; wherein, the processor 7303, The transmitter 7302, the receiver 7307, and the memory 7305 are connected to each other through a bus 7306. The network device 7301 may be the first network device in the foregoing content, and may be, for example, the MME network element in the foregoing content, or may be the SCEF network element or the P-GW network element in the foregoing content. Alternatively, the transceiver can include a transmitter 7302 and a receiver 7307.

Optionally, the memory 7305 can also be used to store program instructions, and the processor 7303 calls the program instructions stored in the memory 7305, can perform one or more steps in the embodiment shown in the above scheme, or alternatively In a manner, the network device 7301 implements the function of the first network device in the foregoing method.

The processor 7303 is configured to control the transmitter 7302 to perform signal transmission according to an instruction to execute the memory storage, and to control the receiver 7306 to perform signal reception. When the processor 7303 executes the memory storage instruction, the receiver 7306 in the network device 7301. The first request is used to receive the identifier of the terminal device, and the processor 7303 is configured to determine the target service platform from the N service platforms that are subscribed by the terminal device, and at least two services exist in the N service platforms. The platform, the at least two service platforms corresponding to the access point name APN are the same, N is an integer greater than 1; the transmitter 7302 is configured to send the first response, wherein the first response is used to indicate between the terminal device and the target service platform establish connection.

In an optional design, the processor 7303 is configured to perform any one of the following: if the first request includes an identifier of the service platform, and the service platform is a service platform that is contracted with the terminal device, The service platform is determined to be the target service platform; if the first request includes the identifier of the service platform, and the service platform is not a service platform contracted with the terminal device, the preset service platform corresponding to the terminal device is determined as the target service platform, and the preset service is The platform is one of the N service platforms. If the identifier of the service platform is not included in the first request, the preset service platform corresponding to the terminal device is determined as the target service platform.

In an optional design, the processor 7303 is further configured to: if the identifier of the service platform is not included in the first request, send a second response to the terminal device by using the transmitter 7302; wherein the second response is used to indicate A connection is not established between the terminal device and the target service platform; or, if the first request includes the identifier of the service platform and the service platform is not a service platform that is contracted with the terminal device, the third response is sent to the terminal device by the transmitter 7302; The third response is used to indicate that no connection is established between the terminal device and the target service platform; or the third response is used to indicate that the connection between the terminal device and the target service platform is not established, and the service platform is not a service platform that is contracted with the terminal device. .

In an optional design, the transmitter 7302 is further configured to: send a create connection request to the second network device; send a first response after receiving the create connection success response; the receiver 7306 is further configured to receive the first The second network device feedback creates a successful connection.

In an optional design, if the network device is the mobility management module MME network element and the second network device is the service capability open function SCEF network element, the connection success response is established between the MME network element and the SCEF network element. After the control plane is connected, if the network device is the MME network element, and the second network device is the packet data network gateway P-GW network element, the connection success response is established by the terminal device and the P-GW network element. Sent after the network PDN connection.

Based on the foregoing content and the same concept, the present application provides a network device for performing any one of the second network device side in the foregoing methods shown in FIG. 2 to FIG. FIG. 11 is a schematic structural diagram of a network device provided by the present application. As shown in FIG. 11, the network device 7401 includes a processor 7403, a transmitter 7402, a receiver 7407, and a memory 7405; wherein, the processor 7403, The transmitter 7402, the receiver 7407, and the memory 7405 are connected to each other through a bus 7406. The network device 7401 may be a second network device in the foregoing content, such as a SCEF network element or a P-GW network element in the foregoing content. Alternatively, the transceiver can include a transmitter 7402 and a receiver 7407.

Alternatively, the memory 7405 can also be used to store program instructions, and the processor 7403 invokes program instructions stored in the memory 7405, can perform one or more of the steps shown in the above scheme, or alternatively In a manner, the network device 7401 implements the functions of the second network device in the foregoing method.

The processor 7403 is configured to control the transmitter 7402 to perform signal transmission according to an instruction to execute the memory storage, and to control the receiver 7406 to perform signal reception. When the processor 7403 executes the memory storage instruction, the receiver 7406 in the network device 7401 And a method for generating a connection sent by the first network device, where the connection request is sent by the first network device after determining the target service platform from the N service platforms subscribed by the terminal device; wherein, among the N service platforms There are at least two service platforms, at least two service platforms corresponding to the same access point name APN; N is an integer greater than 1; the processor 7403 is configured to send after determining that the terminal device establishes a connection with the target service platform The device 7402 sends a create connection success response to the first network device.

In an optional design, if the first network device is the mobility management module MME network element and the network device is the service capability open function SCEF network element, the processor 7403 is configured to: in the MME network element and the SCEF network After establishing a control plane connection between the elements, a connection connection success response is sent to the first network device.

In an optional design, if the first network device is the mobility management module MME network element and the network device is the packet data network gateway P-GW network element, then: the processor 7403 is configured to: in the terminal device and the P After establishing a packet data network PDN connection between the GW network elements, a connection connection success response is sent to the first network device.

In an optional design, the processor 7403 is further configured to: if the target service platform does not configure a preset parameter corresponding to the connection between the terminal device and the target service platform, send the configuration to the target service platform by using the transmitter 7402. The request, wherein the configuration request is used to trigger the target service platform configuration preset parameter; in the case that the target service platform is configured with the preset parameter, the transmitter 7402 sends a create connection success response to the first network device.

In an optional design, the processor 7403 is further configured to: if the target service platform does not configure a preset parameter corresponding to the connection between the terminal device and the target service platform, send a fourth response by using the transmitter 7402; The fourth response is used to indicate that no connection is established between the terminal device and the target service platform; or the fourth response is used to indicate that no connection is established between the terminal device and the target service platform, and the target service platform does not configure the preset parameter.

In an optional design, the first request includes a disaster tolerance flag bit, where the disaster tolerance flag bit is used to indicate whether to enable a disaster tolerance mechanism for the target service platform; the target service platform corresponds to the primary server and the standby server;

The processor 7403 is further configured to monitor, according to the disaster tolerance flag, a link corresponding to the target service platform when the disaster recovery mechanism of the target service platform needs to be started; if the link corresponding to the primary server is in a fault state, and If the link corresponding to the standby server is in a non-fault state, the link corresponding to the standby server is activated, and the mobile originated MO message sent by the received terminal device is sent to the standby server corresponding to the target service platform through the transmitter 7402; If the link corresponding to the primary server is in a non-failure state, the link corresponding to the primary server is activated, the link corresponding to the standby server is deactivated, and the MO message sent by the received terminal device is sent to the target service through the transmitter 7402. The primary server corresponding to the platform.

In an optional design, after determining that the terminal device establishes a connection with the target service platform, the second network device sends a connection connection success response to the first network device, and further includes: a receiver 7406, configured to: receive a modify bearer request sent by the terminal device, where the modify bearer request includes a service platform to be updated, and the sender 7402 is further configured to: send a modify bearer response, where the modify bearer response is used to indicate that the terminal device establishes a connection with the service platform to be updated. .

In an optional design, the processor 7403 is further configured to: if the terminal device transmits the MO message by using the RDS protocol, the second network device carries the port number of the target service platform in the first response.

Based on the above content and the same concept, the present application provides a terminal device for performing any of the terminal device side in the method shown in FIG. 2 to FIG. 9 above. FIG. 12 is a schematic structural diagram of a terminal device provided by the present application. As shown in FIG. 12, the terminal device 7501 includes a processor 7503, a transmitter 7502, a receiver 7507, and a memory 7505; wherein, the processor 7503, The transmitter 7502, the receiver 7507, and the memory 7505 are connected to each other through a bus 7506. Alternatively, the transceiver can include a transmitter 7502 and a receiver 7507.

Optionally, the memory 7505 can also be used to store program instructions, and the processor 7503 calls the program instructions stored in the memory 7505, can perform one or more steps in the embodiment shown in the above scheme, or alternatively In a manner, the terminal device 7501 implements the function of the terminal device in the foregoing method.

The processor 7503 is configured to control the transmitter 7502 to perform signal transmission according to an instruction to execute the memory storage, and control the receiver 7506 to perform signal reception. When the processor 7503 executes the memory storage instruction, the transmitter 7502 in the terminal device 7501 For transmitting the first request, where the first request includes the identifier of the terminal device, and the receiver 7506 is configured to receive the first response, where the first response is the N service platforms that the first network device subscribes from the terminal device. Determining the target service platform and determining that the connection between the terminal device and the target service platform is sent; the first response is used to indicate that the terminal device establishes a connection with the target service platform; and at least two services exist in the N service platforms. For the platform, at least two service platforms have the same access point name APN; N is an integer greater than 1.

In an optional design, the first request includes an identifier of the service platform; wherein, if the service platform is a service platform contracted with the terminal device, the service platform is a target service platform; if the service platform is not contracted with the terminal device The service platform, the default service platform corresponding to the terminal device is the target service platform, and the preset service platform is one of the N service platforms; the first request does not include the identifier of the service platform, and the preset service corresponding to the terminal device The platform is the target service platform.

In the above FIG. 10, FIG. 11 and FIG. 12, any one of the bus 7306, the bus 7406 and the bus 7506 may be a peripheral component interconnect (PCI) bus or an extended industry standard (extended industry standard). Architecture, EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figures 10, 11, and 12, but it does not mean that there is only one bus or one type of bus.

In the above-mentioned FIG. 10, FIG. 11, and FIG. 12, any one of the memory 7305, the memory 7405, and the memory 7505 may include a volatile memory such as a random-access memory (RAM); The memory may also include a non-volatile memory such as a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); the memory may further include the above A combination of types of memory.

In the above FIG. 10, FIG. 11 and FIG. 12, any one of the processor 7303, the processor 7403, and the processor 7503 may be a central processing unit (CPU), a network processor (network processor, NP). ) or a combination of CPU and NP. The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.

Based on the same concept, the embodiment of the present application provides a network device, which is used to perform any solution on the first network device side in the foregoing method flow. FIG. 13 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in FIG. 13, the network device 8301 includes a sending unit 8302, a processing unit 8303, and a receiving unit 8304. The network device 8301 in this example may perform the scheme executed by the first network device corresponding to the above-described FIGS. 2 to 9. The network device 8301 may be the first network device in the foregoing content, and may be, for example, the MME network element in the foregoing content, or may be the SCEF network element or the P-GW network element in the foregoing content.

The receiving unit 8304 is configured to receive a first request, where the first request includes an identifier of the terminal device;

The processing unit 8303 is configured to determine a target service platform from the N service platforms that are subscribed by the terminal device, where at least two service platforms exist in the N service platforms, and the access point names APN corresponding to the at least two service platforms are the same, where N is An integer greater than one;

The sending unit 8302 is configured to send a first response, where the first response is used to indicate that a connection is established between the terminal device and the target service platform.

It should be understood that the division of the units of the above network devices is only a division of logical functions, and the actual implementation may be integrated into one physical entity in whole or in part, or may be physically separated. In the embodiment of the present application, the sending unit 8302 in FIG. 13 may be implemented by the transmitter 7302 of FIG. 10, and the receiving unit 8304 in FIG. 13 may be implemented by the receiver 7307 of FIG. 10, and the processing unit 8303 in FIG. The processor 7303 of 10 is implemented. That is, the sending unit 8302 in the embodiment of the present application may perform the solution executed by the transmitter 7302 of FIG. 10, and the receiving unit 8304 in the embodiment of the present application may perform the solution executed by the receiver 7307 of FIG. 10, which is the present application. In the embodiment, the processing unit 8303 can execute the solution executed by the processor 7303 of FIG. 10, and the rest of the content can be referred to the foregoing content, and details are not described herein again. As shown in FIG. 10 above, the memory 7305 included in the network device 7301 can be used to store a code when the processor 7303 included in the network device 7301 executes a scheme, and the code can be a program/code pre-installed when the network device 7301 is shipped.

Based on the same concept, the embodiment of the present application provides a network device, which is used to perform any solution on the second network device side in the foregoing method flow. FIG. 14 exemplarily shows a schematic structural diagram of a network device according to an embodiment of the present application. As shown in FIG. 14, the network device 8401 includes a sending unit 8402, a processing unit 8403, and a receiving unit 8404. The network device 8401 in this example may perform the scheme executed by the second network device corresponding to the above-described FIGS. 2 to 9. The network device 8401 may be a second network device in the foregoing content, such as a SCEF network element or a P-GW network element in the foregoing content.

The receiving unit 8404 is configured to receive a create connection request sent by the first network device, where the connection request is sent by the first network device after determining the target service platform from the N service platforms subscribed by the terminal device; There are at least two service platforms in the service platform, and at least two service platforms have the same access point name APN; N is an integer greater than one;

The processing unit 8403 is configured to send, by the sending unit 8402, a create connection success response to the first network device after determining that the terminal device establishes a connection with the target service platform.

It should be understood that the division of the units of the above network devices is only a division of logical functions, and the actual implementation may be integrated into one physical entity or all of them physically or partially. In the embodiment of the present application, the sending unit 8402 in FIG. 14 may be implemented by the above-mentioned transmitter 7402 of FIG. 11. The receiving unit 8404 in FIG. 14 may be implemented by the receiver 7407 of FIG. 11 described above, and the processing unit 8403 in FIG. The processor 7403 of 11 is implemented. That is, the sending unit 8402 in the embodiment of the present application may perform the solution executed by the transmitter 7402 of FIG. 11 , and the receiving unit 8404 in the embodiment of the present application may perform the solution executed by the receiver 7407 of the foregoing FIG. 11 . The processing unit 8403 in the embodiment may perform the foregoing implementation of the processor 7403 of FIG. 11, and the rest of the content may be referred to the foregoing content, and details are not described herein again. As shown in FIG. 11 above, the memory 7405 included in the network device 7401 can be used to store a code when the processor 7403 included in the network device 7401 executes a scheme, and the code can be a program/code pre-installed when the network device 7401 is shipped.

Based on the same concept, the embodiment of the present application provides a terminal device for performing any solution on the terminal device side in the foregoing method flow. FIG. 15 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 15, the terminal device 8501 includes a sending unit 8502, a processing unit 8503, and a receiving unit 8504. The terminal device 8501 in this example can execute the scheme executed by the terminal device corresponding to the above-described FIGS. 2 to 9.

a sending unit 8502, configured to send a first request, where the first request includes an identifier of the terminal device;

The receiving unit 8504 is configured to receive the first response, where the first response is that the first network device determines the target service platform from the N service platforms subscribed by the terminal device, and determines that the connection between the terminal device and the target service platform is established. The first response is used to indicate that the terminal device establishes a connection with the target service platform; at least two service platforms exist in the N service platforms, and the access point names APN corresponding to at least two service platforms are the same; N is greater than 1 The integer.

It should be understood that the division of the units of the above network devices is only a division of logical functions, and the actual implementation may be integrated into one physical entity in whole or in part, or may be physically separated. In the embodiment of the present application, the sending unit 8502 in FIG. 15 can be implemented by the transmitter 7502 of FIG. 12, and the receiving unit 8504 in FIG. 15 can be implemented by the receiver 7507 of FIG. 12, and the processing unit 8503 in FIG. The processor 7503 of 12 is implemented. That is, the sending unit 8502 in the embodiment of the present application may perform the solution executed by the transmitter 7502 of the foregoing FIG. 12, and the receiving unit 8504 in the embodiment of the present application may perform the solution executed by the receiver 7507 of the foregoing FIG. The processing unit 8503 in the embodiment may perform the foregoing implementation of the processor 7503 of FIG. 12, and the rest may refer to the foregoing content, and details are not described herein again. As shown in FIG. 12 above, the memory 7505 included in the terminal device 7501 can be used to store a code when the processor 7503 included in the terminal device 7501 executes a scheme, and the code can be a program/code pre-installed when the terminal device 7501 is shipped.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof, and when implemented using a software program, may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The instructions may be stored on a computer storage medium or transferred from one computer storage medium to another computer storage medium, for example, instructions may be wired from a website site, computer, server or data center (eg, coaxial cable, fiber optic, digital user) Line (DSL) or wireless (eg infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center. The computer storage medium can be any available media that can be accessed by the computer or a data storage device such as a server, data center, or the like, including one or more available media. Usable media can be magnetic media (eg, floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical media (eg, CD, DVD, BD, HVD, etc.), or semiconductor media (eg, ROM, EPROM, EEPROM, Non-volatile memory (NAND FLASH), solid state disk (SSD), etc.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowcharts and/or block diagrams, and combinations of flow and/or blocks in the flowcharts and/or <RTIgt; These instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine such that instructions executed by a processor of a computer or other programmable data processing device are utilized for implementation A means of function specified in a flow or a flow and/or a block diagram of a block or blocks.

The instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. A function specified in a block or blocks of a flow or a flow and/or a block diagram of a flow chart.

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

It is apparent that those skilled in the art can make various modifications and variations to the embodiments of the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the embodiments of the present invention.

Claims

A communication method for a narrowband Internet of Things NB-IoT network, comprising:

Receiving, by the first network device, a first request, where the first request includes an identifier of the terminal device;

Determining, by the first network device, the target service platform from the N service platforms that are subscribed by the terminal device, where there are at least two service platforms, and the access points corresponding to the at least two service platforms The name APN is the same, and the N is an integer greater than one;

The first network device sends a first response, where the first response is used to indicate that a connection is established between the terminal device and the target service platform.
The method according to claim 1, wherein the first network device determines a target service platform from the N service platforms subscribed by the terminal device, including any one of the following contents:

If the first request includes the identifier of the service platform, and the service platform is a service platform that is contracted with the terminal device, the first network device determines the service platform as the target service platform;

If the first request includes the identifier of the service platform, and the service platform is not a service platform that is contracted with the terminal device, the first network device determines the preset service platform corresponding to the terminal device. For the target service platform, the preset service platform is one of the N service platforms;

If the identifier of the service platform is not included in the first request, the first network device determines the preset service platform corresponding to the terminal device as the target service platform.
The method of claim 1, wherein after receiving the first request, the method further comprises:

If the identifier of the service platform is not included in the first request, the first network device sends a second response to the terminal device, where the second response is used to indicate the terminal device and the target service No connection is established between the platforms;

or,

If the first request includes the identifier of the service platform and the service platform is not a service platform that is contracted with the terminal device, the first network device sends the third response to the terminal device; The third response is used to indicate that no connection is established between the terminal device and the target service platform; or the third response is used to indicate that no connection is established between the terminal device and the target service platform. And the service platform is not a service platform contracted with the terminal device.
The method according to claim 1 or 2, wherein, after the first network device determines the target service platform from the N service platforms that are subscribed by the terminal device, before sending the first response, the method further includes:

Sending, by the first network device, a create connection request to the second network device;

Receiving, by the first network device, a connection establishment success response fed back by the second network device;

Sending, by the first network device, the first response, including:

The first network device sends the first response after receiving the create connection success response.
The method according to claim 4, wherein if the first network device is a mobility management module MME network element and the second network device is a service capability open function SCEF network element, the connection is successfully established. The response is sent after the MME network element establishes a control plane connection with the SCEF network element;

If the first network device is an MME network element, and the second network device is a packet data network gateway P-GW network element, the creating a connection success response is the terminal device and the P-GW network element. Transmitted after establishing a packet data network PDN connection.
A communication method for a narrowband Internet of Things NB-IoT network, comprising:

The second network device receives the create connection request sent by the first network device, where the create connection request is sent by the first network device after determining the target service platform from the N service platforms subscribed by the terminal device; There are at least two service platforms in the N service platforms, and the access point names APN corresponding to the at least two service platforms are the same; the N is an integer greater than 1.

After determining that the terminal device establishes a connection with the target service platform, the second network device sends a create connection success response to the first network device.
The method according to claim 6, wherein if the first network device is a mobility management module MME network element and the second network device is a service capability open function SCEF network element, then:

After determining that the terminal device establishes a connection with the target service platform, the second network device sends a connection connection success response to the first network device, including:

After establishing a control plane connection between the MME network element and the SCEF network element, the SCEF network element sends a create connection success response to the first network device.
The method according to claim 6, wherein if the first network device is a mobility management module MME network element and the second network device is a packet data network gateway P-GW network element, then:

After determining that the terminal device establishes a connection with the target service platform, the second network device sends a connection connection success response to the first network device, including:

After the P-GW network element establishes a packet data network PDN connection between the terminal device and the P-GW network element, the P-GW network element sends a create connection success response to the first network device.
The method according to any one of claims 6 to 8, wherein after the second network device receives the create connection request sent by the first network device, before sending the connection connection success response to the first network device, Also includes:

If the target service platform does not configure a preset parameter corresponding to the connection between the terminal device and the target service platform, then:

The second network device sends a configuration request to the target service platform, where the configuration request is used to trigger the target service platform to configure the preset parameter;

After determining that the terminal device establishes a connection with the target service platform, the second network device sends a connection connection success response to the first network device, including:

And the second network device sends a create connection success response to the first network device if the target service platform configures the preset parameter.
The method according to any one of claims 6 to 8, wherein after the second network device receives the create connection request sent by the first network device, the method further includes:

If the target service platform does not configure a preset parameter corresponding to the connection between the terminal device and the target service platform, then:

Sending, by the second network device, a fourth response;

The fourth response is used to indicate that no connection is established between the terminal device and the target service platform; or the fourth response is used to indicate that the terminal device and the target service platform are not established. Connected, and the target service platform is not configured with the preset parameters.
The method according to any one of claims 6 to 10, wherein the first request includes a disaster tolerance flag bit, wherein the disaster tolerance flag bit is used to indicate whether to enable disaster recovery for the target service platform. mechanism;

The target service platform corresponds to a primary server and a standby server;

After the determining, by the second network device, the connection between the terminal device and the target service platform, after the connection is successfully sent to the first network device, the second network device further includes:

The second network device monitors, according to the disaster tolerance flag, a link corresponding to the target service platform when determining that the disaster tolerance mechanism for the target service platform needs to be enabled;

If the link corresponding to the primary server is in a fault state, and the link corresponding to the standby server is in a non-failure state, the link corresponding to the standby server is activated, and the received terminal device sends the received Sending the mobile originating MO message to the standby server corresponding to the target service platform;

If the link corresponding to the primary server is in a non-failure state, activate the link corresponding to the primary server, deactivate the link corresponding to the standby server, and send the received MO of the terminal device The message is sent to the primary server corresponding to the target service platform.
The method according to any one of claims 6 to 11, wherein after the determining, by the second network device, the connection between the terminal device and the target service platform, the method further comprises:

Receiving, by the second network device, a modify bearer request sent by the terminal device, where the modify bearer request includes a service platform to be updated;

The second network device sends a modify bearer response, where the modify bearer response is used to indicate that the terminal device establishes a connection with the to-be-updated service platform.
A communication method for a narrowband Internet of Things NB-IoT network, comprising:

The terminal device sends a first request, where the first request includes an identifier of the terminal device;

The terminal device receives the first response, where the first response is that the first network device determines the target service platform from the N service platforms subscribed by the terminal device, and determines the terminal device and the target service. The first response is used to indicate that the terminal device establishes a connection with the target service platform; the N service platforms have at least two service platforms, and the at least two The access point names APN corresponding to the service platforms are the same; the N is an integer greater than 1.
The method of claim 13, wherein the first request includes an identifier of a service platform; wherein, if the service platform is a service platform that is contracted with the terminal device, the service platform is a target service platform, where the service platform is a service platform that is not contracted with the terminal device, the preset service platform corresponding to the terminal device is the target service platform, and the preset service platform is the N One of the service platforms;

The identifier of the service platform is not included in the first request, and the preset service platform corresponding to the terminal device is the target service platform.
A network device, comprising:

a receiver, configured to receive a first request, where the first request includes an identifier of the terminal device;

a processor, configured to determine a target service platform from the N service platforms that are subscribed by the terminal device, where at least two service platforms exist, and the access point names corresponding to the at least two service platforms APN is the same, the N is an integer greater than one;

And a transmitter, configured to send a first response, where the first response is used to indicate that a connection is established between the terminal device and the target service platform.
The network device according to claim 15, wherein said processor is configured to perform any one of the following:

If the first request includes an identifier of the service platform, and the service platform is a service platform that is contracted with the terminal device, determining the service platform as the target service platform;

If the first request includes the identifier of the service platform, and the service platform is not a service platform that is contracted with the terminal device, determining a preset service platform corresponding to the terminal device as the target service platform The preset service platform is one of the N service platforms;

If the identifier of the service platform is not included in the first request, determining the preset service platform corresponding to the terminal device as the target service platform.
The network device according to claim 15, wherein the processor is further configured to:

And if the identifier of the service platform is not included in the first request, sending, by the sender, a second response to the terminal device, where the second response is used to indicate the terminal device and the target service platform No connection has been established between them;

or,

And if the first request includes the identifier of the service platform, and the service platform is not a service platform that is contracted with the terminal device, sending, by the sender, the third response to the terminal device, where The third response is used to indicate that no connection is established between the terminal device and the target service platform; or the third response is used to indicate that no connection is established between the terminal device and the target service platform. And the service platform is not a service platform that is contracted with the terminal device.
The network device according to claim 15 or 16, wherein the transmitter is further configured to: send a create connection request to the second network device; and send the first response after receiving the create connection success response ;

The receiver is further configured to receive the create connection success response fed back by the second network device.
The network device according to claim 18, wherein if the network device is a mobility management module MME network element and the second network device is a service capability open function SCEF network element, the creating a connection is successfully responded. And sending, after the MME network element establishes a control plane connection with the SCEF network element;

If the network device is a MME network element, and the second network device is a packet data network gateway P-GW network element, the creating a connection success response is between the terminal device and the P-GW network element. Established after the packet data network PDN connection is established.
A network device, comprising:

a receiver, configured to receive a create connection request sent by the first network device, where the create connection request is sent by the first network device after determining the target service platform from the N service platforms subscribed by the terminal device; At least two service platforms exist in the N service platforms, where the access point names APN corresponding to the at least two service platforms are the same; the N is an integer greater than 1.

And a processor, configured to send, by using a transmitter, a create connection success response to the first network device after determining that the terminal device establishes a connection with the target service platform.
The network device according to claim 20, wherein, if the first network device is a mobility management module MME network element, and the network device is a service capability open function SCEF network element, then:

The processor is configured to:

After establishing a control plane connection between the MME network element and the SCEF network element, sending a create connection success response to the first network device.
The network device according to claim 20, wherein if the first network device is a mobility management module MME network element and the network device is a packet data network gateway P-GW network element, then:

The processor is configured to:

After establishing a packet data network PDN connection between the terminal device and the P-GW network element, sending a connection connection success response to the first network device.
The network device according to any one of claims 20 to 22, wherein the processor is further configured to:

And if the target service platform does not configure a preset parameter corresponding to the connection between the terminal device and the target service platform, sending, by the sender, a configuration request to the target service platform, where the configuration request And configured to trigger the target service platform to configure the preset parameter;

And in the case that the target service platform configures the preset parameter, sending, by the sender, a create connection success response to the first network device.
The network device according to any one of claims 20 to 22, wherein the processor is further configured to:

And if the target service platform does not configure a preset parameter corresponding to the connection between the terminal device and the target service platform, sending a fourth response by using the transmitter;

The fourth response is used to indicate that no connection is established between the terminal device and the target service platform; or the fourth response is used to indicate that the terminal device and the target service platform are not established. Connected, and the target service platform is not configured with the preset parameters.
The network device according to any one of claims 20 to 24, wherein the first request includes a disaster tolerance flag bit, wherein the disaster tolerance flag bit is used to indicate whether to open the capacity of the target service platform. Disaster mechanism;

The target service platform corresponds to a primary server and a standby server;

The processor is further configured to:

According to the disaster tolerance flag, when the disaster tolerance mechanism of the target service platform needs to be started, the link corresponding to the target service platform is monitored;

If the link corresponding to the primary server is in a fault state, and the link corresponding to the standby server is in a non-failure state, the link corresponding to the standby server is activated, and the received terminal device sends the received The mobile originating MO message is sent by the sender to the standby server corresponding to the target service platform;

If the link corresponding to the primary server is in a non-failure state, activate the link corresponding to the primary server, deactivate the link corresponding to the standby server, and send the received MO of the terminal device The message is sent by the sender to the primary server corresponding to the target service platform.
The network device according to any one of claims 20 to 25, wherein the second network device, after determining that the terminal device establishes a connection with the target service platform, to the first network device Send a successful connection to create a connection, also includes:

The receiver is further configured to: receive a modify bearer request sent by the terminal device, where the modify bearer request includes a service platform to be updated;

The transmitter is further configured to: send a modify bearer response, where the modify bearer response is used to indicate that the terminal device establishes a connection with the to-be-updated service platform.
The network device according to any one of claims 20 to 26, wherein the processor is further configured to:

If the terminal device transmits the MO message through the RDS protocol, the second network device carries the port number of the target service platform in the first response.
A terminal device, comprising:

a transmitter, configured to send a first request, where the first request includes an identifier of the terminal device;

a receiver, configured to receive a first response, where the first response is that the first network device determines a target service platform from the N service platforms subscribed by the terminal device, and determines the terminal device and the target The first response is used to indicate that the terminal device establishes a connection with the target service platform; and at least two service platforms exist in the N service platforms, where the at least two service platforms are present. The access point names APN corresponding to the two service platforms are the same; the N is an integer greater than 1.
The terminal device according to claim 28, wherein the first request includes an identifier of a service platform; wherein, if the service platform is a service platform that is contracted with the terminal device, the service platform is The target service platform; if the service platform is a service platform that is not contracted with the terminal device, the preset service platform corresponding to the terminal device is the target service platform, and the preset service platform is the One of the N service platforms;

The identifier of the service platform is not included in the first request, and the preset service platform corresponding to the terminal device is the target service platform.
A computer storage medium, characterized in that the computer storage medium stores computer executable instructions that, when invoked by a computer, cause the computer to perform any of claims 1 to 14 The method described.