CN107438290B

CN107438290B - Connection establishment method for small data transmission, SCEF entity and MME

Info

Publication number: CN107438290B
Application number: CN201610352681.7A
Authority: CN
Inventors: 李志军; 黄梅青
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-05-25
Filing date: 2016-05-25
Publication date: 2021-07-20
Anticipated expiration: 2036-05-25
Also published as: CN107438290A; WO2017202194A1

Abstract

The invention discloses a connection establishment method for small data transmission, an SCEF entity and an MME, wherein the method comprises the following steps: after receiving the SCEF connection establishment request sent by the MME, the SCEF entity checks the information of the third-party service equipment, and rejects the SCEF connection establishment request according to the check result of the information of the third-party service equipment.

Description

Connection establishment method for small data transmission, SCEF entity and MME

Technical Field

The present invention relates to non-IP data connection establishment technologies, and in particular, to a connection establishment method for small data transmission, a Service Capability Exposure Function (SCEF) Entity, and a Mobility Management unit (MME).

Background

The rapid development of the Internet of Things (IoT) brings a great challenge to the Evolved packet domain system (EPS) defined by the third Generation Partnership Project (3 GPP). Among terminals (UEs) applied to the internet of things, there is a typical Narrow bandwidth internet of things terminal (NB-IoT UE, Narrow Band IoT UE). When a narrow bandwidth internet of things terminal (NB-IoT UE) accesses a network, the amount of effective data to be transmitted or received is usually small, but in order to initiate data from an IDLE state (IDLE) to a CONNECTED state (CONNECTED), the network signaling itself is operated to be much larger than the amount of data to be transmitted or received. Therefore, the large amount of access of the NB-iot easily causes the network signaling load to be too high, causes network congestion, and brings low benefit to the operator. On the other hand, data transmitted by a narrow bandwidth internet of things terminal (NB-IoT UE) may be non-IP, and the design of a data transmission link in the existing EPS is based on IP transmission, and how to transmit non-IP data also provides challenges for the conventional EPS network.

In order to adapt to the development of mobile internet of things communication, 3GPP enhances the architecture of the existing EPS and simplifies the access flow of a narrow bandwidth internet of things terminal (NB-IoT UE), so that the EPS can adapt to the access and data transmission of the NB-IoT UE.

Fig. 1 shows an enhancement performed by an existing EPS system to Access a terminal of the internet of things with a narrow bandwidth, which mainly includes two parts, namely an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and an Evolved Packet Core Network (EPC).

In an E-UTRAN radio access network, a base station (eNodeB) is included.

In the EPC packet core network, a Home Subscriber data Server (HSS), a Mobility Management Element (MME), a Serving Gateway (S-GW), a packet data network Gateway (P-GW, PDN Gateway) are included, where:

home Subscriber Server (HSS): the permanent storage place of the user subscription data is positioned in the home network of the user subscription;

a mobility management unit: the method is characterized in that the user subscription data is stored in the current network and is responsible for Non-Access Stratum (NAS) signaling management from a terminal to the network, tracking and paging management functions and bearer management in an idle mode of a user;

serving Gateway (S-GW): the gateway from a core network to a wireless system is responsible for user plane bearing from a terminal to the core network, data caching in a terminal idle mode, a function of initiating a service request by a network side, and functions of lawful interception, packet data routing and forwarding;

packet data network Gateway (P-GW, PDN Gateway): the system is an Evolved Packet System (EPS) and a gateway of an external network of the system, and is responsible for functions of IP address allocation, a charging function, packet filtering, policy application and the like of a terminal.

In addition, in order to support non-IP data transmission of the narrow bandwidth internet of things terminal, the 3GPP introduces a Service Capability Exposure Function (SCEF). The SCEF, also commonly referred to AS a Capability openness platform, is used to establish a T6 connection (also referred to AS SCEF connection) dedicated to transmitting non-IP data between the MME and the SCEF, so AS to receive a non-IP small packet carried by the UE in NAS signaling from the MME and send the non-IP small packet to a third party Service platform (SCS) or a third party Application Server (AS), or receive a non-IP small packet from the SCS/AS and send the non-IP small packet to the MME.

Fig. 2 is a schematic flowchart of the NB-IoT UE attaching to the network and implementing non-IP data transmission under the architecture based on fig. 1, and has the following steps:

2A 01-2A 07, a UE attaches to a network and establishes a connection for transmitting non-IP data.

2A01, the UE initiates an attach request to the MME.

In the attach request, the access capability information of the internet of things of the UE is carried, such as whether the UE supports control over an optimized transmission mode, whether the UE supports a user plane optimized transmission mode, and the like;

2A02, MME sends a location update request to HSS;

2A03, the HSS returns a location update response to the MME, and the message carries UE subscription data;

specifically, in this example, the subscription data includes at least one specific Access Point Name (APN) configuration for the MME to establish a PDN connection to the SCEF, where the SCEF connection may be used to transmit non-IP small data, and of course, may also be used to transmit IP small data.

Specifically, the APN configuration includes: connection type indication, SCEF identification (SCEF ID), etc. A connection type indication indicating whether the APN is used to establish a SCEF-oriented connection or a PGW-oriented connection. The SCEF identifies from which the IP address of the SCEF can be derived, typically the full domain name of the SCEF, which can uniquely identify an SCEF.

2a04, the MME initiates a SCEF connection establishment request to the SCEF, which includes an APN name and an EPS Bearer identity (EPS Bearer ID);

and the MME acquires the SCEF address according to the APN configuration in the UE subscription data and sends an SCEF connection establishment request to the SCEF. If there are multiple APNs configured in the UE subscription data for establishing the SCEF connection, the MME configures the UE for each APN to establish a corresponding SCEF connection.

For each SCEF connection, only one EPS bearer is currently created, i.e. the MME allocates only one EPS bearer identity for the SCEF connection.

2A05, the SCEF receives the SCEF connection establishment request of the MME, establishes the SCEF connection for the UE, and returns an SCEF connection establishment response to the MME;

2A06, the MME returns an attachment response to the UE;

in the attach response, the MME returns the CIOT capabilities supported by the network, such as whether the network supports control-over-optimization transport, whether the network supports user plane-optimization transport, and so on.

In the attach response, the information of the SCEF connection established for the UE is also included, such as: IP address, EPS bearer identification, etc.

Thereafter, the UE enters an idle state.

2B 01-2B 04, the SCS/AS initiates a non-IP data transmission configuration process to the network. In particular, the amount of the solvent to be used,

2B01, SCS/AS sends a non-IP data transfer configuration request to SCEF, including SCS identification (SCS-ID), SCS Reference number (SCS-Reference-ID) in the request;

after receiving the non-IP data transmission configuration request of SCS/AS, SCEF locally stores SCS identification and SCS reference number. When the UE initiates uplink small data transmission, the SCEF uses the information to send the small data to the correct SCS/AS.

2B02, the SCEF sends a data transmission authorization request to the HSS, and the request comprises an SCEF identification (SCEF-ID) and an APN name;

2B03, the HSS performs authorization check on the SCEF and returns a data transmission authorization response;

after receiving the data transmission authorization request, the HSS performs authorization check on the APN and SCEF identifiers provided by the SCEF according to the APN and SCEF identifiers in the APN configuration. If the APN and the SCEF identification provided by the SCEF are not consistent with the APN and the SCEF identification in the APN configuration, the authorization check fails, and the HSS returns a failure response.

2B04, after receiving the data transmission authorization response, the SCEF returns a data transmission configuration response to the SCS/AS;

2C 01-2C 08, the UE initiates an uplink small data transmission process.

2C01, the UE initiates an RRC connection request to the eNodeB from an idle state;

in this example, the UE carries a NAS packet in the RRC connection message, where the NAS packet carries an uplink small packet to be sent by the UE, and the small packet may be a non-IP small packet or an IP small packet.

And simultaneously, the NAS data packet comprises an EPS bearer identifier corresponding to an EPS bearer used by the UE to send the uplink small data packet. Using the bearer identity, the MME may forward the small data packet sent by the UE to the correct SCEF.

2C02, the eNodeB initiates an uplink NAS data transmission request to the MME, wherein the uplink NAS data transmission request carries the NAS data packet in the previous step;

2C03, MME receives the uplink NAS data transmission request sent by eNodeB, and sends an initial data transmission message to SCEF, wherein the initial data transmission message carries a small data packet sent by UE;

after receiving the eNodeB message, the MME extracts a small data packet to be sent by the UE from the NAS data packet, encapsulates the small data packet in an origination data transmission message, and sends the origination data transmission message to the SCEF. The MME sends an originating data transmission request to the SCEF according to the SCEF connection established in the previous step.

2C04, after the SCEF receives the initial data transmission request sent by the MME, the SCEF initiates a data transmission request to the SCS/AS on an external API interface, and the data transmission request carries a small data packet sent by the UE;

2C05, the SCS/AS returns a data transmission response to the SCEF, where the data transmission response may carry a downlink small data packet to be sent by the SCS/AS to the UE, and the small data packet may be a non-IP small data packet or an IP small data packet;

2C06, the SCEF returns an origination data transmission response to the MME, which may carry a small data packet that the SCS/AS is to send to the UE;

it should be clear that whether the SCEF initiates the 2C06 step after waiting for the steps 2C 04-2C 05 to complete depends on the SCEF implementation.

2C07, the MME returning an uplink NAS data transmission response to the eNodeB, which may carry NAS packets to carry small packets destined for the UE;

2C08, the eNodeB returns an RRC connection response, possibly an NAS packet, to the UE to carry a small packet to be sent to the UE;

in the above procedure, when the UE attaches to the network, the MME establishes the SCEF connection for the UE only according to the APN configuration in the UE subscription data. Before the UE intends to send the uplink decimal packet, the SCEF may not receive the data transmission configuration message sent by the SCS/AS yet. That is, even if the UE initiates the origination of the small data transmission, the uplink small data packet sent by the UE can only be sent to the SCEF, but cannot be sent to the SCS/AS. At this time, the SCEF may discard the uplink small data packet sent by the UE or temporarily buffer the uplink small data packet for a certain period of time.

For the UE, if the UE wants the SCS/AS to respond to the uplink small data packet sent by the UE, that is, wants the SCS/AS to return the downlink small data packet, the UE may attempt to send the uplink small data multiple times when the downlink small data returned by the SCS/AS is not received, however, the attempt will fail and the network signaling will be wasted.

Disclosure of Invention

In order to solve the above technical problem, embodiments of the present invention provide a connection establishment method for small data transmission, an SCEF entity, and an MME.

The method for establishing the connection of the small data transmission provided by the embodiment of the invention comprises the following steps:

after receiving the SCEF connection establishment request sent by the MME, the SCEF entity checks the information of the third-party service equipment, and rejects the SCEF connection establishment request according to the check result of the information of the third-party service equipment.

In this embodiment of the present invention, the checking the third-party service device information includes:

the SCEF entity checks whether a data transmission configuration request of the corresponding third-party service equipment exists at present;

correspondingly, the rejecting the SCEF connection establishment request according to the checking result of the third party service device information includes:

and when the SCEF entity determines that the data transmission configuration request of the corresponding third-party service equipment does not exist, rejecting the SCEF connection establishment request.

In this embodiment of the present invention, after rejecting the SCEF connection establishment request, the method further includes:

the SCEF sends an SCEF connection establishment response to the MME; the SCEF connection establishment response carries non-IP data connection state information.

In this embodiment of the present invention, the non-IP data connection status information includes:

non-IP data transport configuration is not performed or SCEF connection is not available.

after receiving the data transmission configuration request sent by the third-party service equipment, the SCEF sends a data transmission authorization request to a Home Subscriber Server (HSS);

receiving a data transmission authorization response sent by the HSS, wherein the data transmission authorization response carries service node information;

and sending an SCEF connection establishment request to an MME according to the service node information, so that the MME establishes the SCEF connection according to the SCEF connection establishment request.

after receiving the data transmission configuration request sent by the third-party service equipment, the SCEF sends a data transmission authorization request to a Home Subscriber Server (HSS), so that the HSS sends subscription data information to the MME, wherein the subscription data information comprises configuration information of an Access Point Name (APN) used for establishing SCEF connection; sending an SCEF connection establishment request to the SCEF by the MME according to the configuration information of the APN;

and the SCEF establishes the SCEF connection according to the SCEF connection establishment request.

The SCEF entity provided in the embodiments of the present invention includes: a receiving unit, a checking unit and a first connection establishing unit, wherein:

a receiving unit, configured to receive an SCEF connection establishment request sent by a mobility management unit MME;

a checking unit for checking the third party service device information;

and the first connection establishing unit is used for rejecting the SCEF connection establishing request according to the checking result of the third-party service equipment information.

In the embodiment of the present invention, the checking unit is further configured to check whether there is a data transmission configuration request of the third-party service device corresponding to the current data transmission configuration request;

correspondingly, the first connection establishing unit is further configured to reject the SCEF connection establishment request when it is determined that there is no corresponding data transmission configuration request of the third-party service device.

In an embodiment of the present invention, the SCEF entity further includes:

a first sending unit, configured to send an SCEF connection establishment response to the MME; the SCEF connection establishment response carries non-IP data connection state information.

In an embodiment of the present invention, the SCEF entity further includes: a second transmission unit and a third transmission unit, wherein:

the receiving unit is further configured to receive a data transmission configuration request sent by the third-party service device, and correspondingly, the second sending unit is configured to send a data transmission authorization request to a home subscriber server HSS;

the receiving unit is further configured to receive a data transmission authorization response sent by the HSS, where the data transmission authorization response carries service node information;

a third sending unit, configured to send, according to the service node information, an SCEF connection establishment request to an MME, so that the MME establishes an SCEF connection according to the SCEF connection establishment request.

In an embodiment of the present invention, the SCEF entity further includes: a fourth sending unit and a second connection establishing unit, wherein:

the receiving unit is further configured to receive a data transmission configuration request sent by the third-party service device, and correspondingly, the fourth sending unit is configured to send a data transmission authorization request to a home subscriber server HSS, so that the HSS sends subscription data information to the MME, where the subscription data information includes configuration information of an access point name APN used for establishing a SCEF connection; and the MME sends an SCEF connection establishment request to the SCEF according to the configuration information of the APN;

and the second connection establishing unit is used for establishing the SCEF connection according to the SCEF connection establishing request.

The mobility management unit provided by the embodiment of the invention comprises: a first sending unit, a first receiving unit, a second receiving unit and a connection establishing unit, wherein:

a first sending unit, configured to send an SCEF connection establishment request to an SCEF entity with a service capability openness function;

a first receiving unit, configured to receive an SCEF connection establishment response sent by the SCEF entity; the SCEF connection establishment response carries non-IP data connection state information;

a second receiving unit, configured to receive a connection establishment request sent by the SCE;

and the connection establishing unit is used for establishing the SCEF connection according to the SCEF connection establishing request.

The mobility management unit provided by the embodiment of the invention comprises: a first transmitting unit, a first receiving unit and a second transmitting unit, wherein:

a first receiving unit, configured to receive subscription data information sent by a home subscriber server HSS, where the subscription data information includes configuration information of an access point name APN used for establishing an SCEF connection;

and a second sending unit, configured to send an SCEF connection establishment request to an SCEF according to the configuration information of the APN.

According to the connection establishment method for small data transmission, the SCEF entity and the MME of the embodiment of the invention, after the SCEF entity receives the SCEF connection establishment request sent by the MME, the establishment of the SCEF connection cannot be understood, but the information of third-party service equipment such AS SCS/AS is checked, and whether the SCEF connection is established or not is determined according to the check result. The technical scheme of the embodiment of the invention ensures that the network side can manage the establishment and the use of the SCEF connection, avoids the condition that the terminal initiates the transmission of the uplink small data and cannot correctly send the uplink small data to the SCS/AS, and can further inform the terminal that the current SCEF connection is temporarily unavailable, so that the UE does not need to try to send the uplink small data for many times, thereby avoiding the waste of network signaling.

Drawings

FIG. 1 is a schematic diagram of the architecture of an enhanced EPS system;

fig. 2 is a schematic flow chart of non-IP data transmission implemented when a UE based on the network architecture shown in fig. 1 is attached to a network;

fig. 3 is a flowchart of a connection establishment method for small data transmission according to a first embodiment of the present invention;

fig. 4 is a flowchart of a connection establishment method for small data transmission according to a second embodiment of the present invention;

fig. 5 is a flowchart of a connection establishment method for small data transmission according to application example one of the present invention;

fig. 6 is a flowchart of a connection establishment method for small data transmission according to application example two of the present invention;

fig. 7 is a schematic structural diagram of the SCEF entity according to the embodiment of the present invention;

FIG. 8 is a schematic structural diagram of an MME according to a first embodiment of the invention;

fig. 9 is a schematic structural diagram of an MME according to a second embodiment of the present invention.

Detailed Description

So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.

Fig. 3 is a flowchart of a small data transmission connection establishment method according to an embodiment of the present invention, and as shown in fig. 3, the small data transmission connection establishment method according to the embodiment of the present invention includes the following processing steps:

step 301, after receiving the SCEF connection establishment request sent by the mobility management unit MME, the SCEF entity checks the third party service device information.

In the embodiment of the present invention, the third-party Service device includes a third-party Service platform (SCS) or a third-party Application Server (AS).

Step 302, the SCEF entity rejects the SCEF connection establishment request according to the check result of the third party service device information.

In the embodiment of the invention, the information of the third-party service equipment is checked, namely, whether the data transmission configuration request of the corresponding third-party service equipment exists or not is checked, namely, whether the SCS requests a non-IP data transmission configuration process or not is checked, and if the SCS does not request the non-IP data transmission configuration process, the SCEF connection establishment request is rejected.

Specifically, the SCEF entity checks whether there is a data transmission configuration request of the third-party service device corresponding to the SCEF entity at present; and rejecting the SCEF connection establishment request when determining that no corresponding data transmission configuration request of the third-party service equipment exists.

Step 303, the SCEF sends a SCEF connection establishment response to the MME.

The SCEF connection establishment response carries non-IP data connection state information. Wherein the non-IP data connection status information comprises: non-IP data transport configuration is not performed or SCEF connection is not available.

Step 304, after receiving the data transmission configuration request sent by the third party service equipment, the SCEF sends a data transmission authorization request to the HSS.

Step 305, the SCEF receives a data transmission authorization response sent by the HSS, where the data transmission authorization response carries service node information.

Step 306, the SCEF sends an SCEF connection establishment request to the MME according to the serving node information, so that the MME establishes an SCEF connection according to the SCEF connection establishment request.

Fig. 4 is a flowchart of a small data transmission connection establishment method according to a second embodiment of the present invention, and as shown in fig. 4, the small data transmission connection establishment method according to the second embodiment of the present invention includes the following processing steps:

step 401, after receiving the SCEF connection establishment request sent by the mobility management unit MME, the SCEF entity checks the third party service device information.

Step 402, the SCEF entity rejects the SCEF connection establishment request according to the check result of the third party service device information.

In the embodiment of the invention, the information of the third-party service equipment is checked, namely, whether the data transmission configuration request of the third-party service equipment corresponding to the information exists or not is checked, namely, whether the SCS requests a non-IP data transmission configuration process or not is checked, and if the SCS does not request the non-IP data transmission configuration process, the SCEF connection establishment request is rejected.

Step 403, the SCEF sends a SCEF connection establishment response to the MME.

Step 404, the SCEF receives a data transmission configuration request sent by the third party service equipment; and then sends a data transfer authorization request to the HSS.

After receiving the data transmission authorization request, the HSS sends subscription data information to the MME, wherein the subscription data information comprises configuration information of an access point name APN for establishing SCEF connection; and the MME sends an SCEF connection establishment request to the SCEF according to the configuration information of the APN.

Step 405, the SCEF establishes an SCEF connection according to the SCEF connection establishment request.

The technical solution of the embodiment of the present invention is further described in detail by using specific application examples.

Application example one

Fig. 5 is a flowchart of a connection establishment method for small data transmission according to an application example of the present invention, and AS shown in fig. 5, the SCEF according to the embodiment of the present invention determines whether to allow the MME to create the SCEF connection or notify the MME to create the SCEF connection according to the SCS/AS information.

As shown in fig. 5, the present application example includes the following processing steps:

5A 01-5A 06, the UE is attached to the network, and the SCEF rejects the SCEF connection establishment request initiated by the MME according to the SCS/AS information. In particular, the amount of the solvent to be used,

5A01, UE initiates an attach request to MME;

5A02, MME sends a location update request to HSS;

5A03, the HSS returns a location update response to the MME, and the UE subscription data contains APN configuration information used for creating SCEF connection;

5A04, MME sends SCEF connection establishment request to SCEF;

5A05, the SCEF judges whether to allow the SCEF connection establishment request according to the SCS/AS information;

in step 5a05, the SCEF checks the SCS/AS information, i.e. checks whether there is a corresponding SCS/AS information for the SCEF connection, i.e. whether there is a SCS/AS requesting a non-IP data transmission configuration flow.

And if the SCS/AS does not request the non-IP data transmission configuration process, rejecting the SCEF connection establishment request.

5A06, the SCEF returns an SCEF connection establishment response to the MME, wherein the SCEF carries a non-IP data connection state;

in this step, the non-IP data connection state may be: non-IP data transport configuration is not performed or SCEF connection is not available. The non-IP data connection status may be indicated by a failure reason.

5a07, the MME returns an attach response to the UE, and because the SCEF connection is not successfully established, the attach response does not include SCEF connection information;

thereafter, the UE enters an idle state.

5B 01-5B 06, the SCS/AS sends a data transmission configuration request to the SCEF, and the SCEF initiates SCEF connection establishment to the MME. In particular, the amount of the solvent to be used,

5B01, SCS/AS sends data transmission configuration request to SCEF;

5B02, the SCEF sending a data transfer authorization request to the HSS;

5B03, the HSS performs authorization check on the SCEF and returns a data transmission authorization response;

in this step, the HSS returns the current serving node information, i.e. the current MME information, to the SCEF. With the serving node information, the SCEF may actively initiate SCEF connection establishment to the MME.

5B04, after receiving the data transmission authorization response, the SCEF returns a data transmission configuration response to the SCS/AS;

5B05, the SCEF sends a SCEF connection establishment request message to the MME;

5B06, the MME agrees to the SCEF connection establishment request, and sends an SCEF connection establishment response message to the SCEF.

5B07, the MME sends a bearer establishment notification to the UE, carrying information of the SCEF connection that has been established. If the UE is currently in an IDLE state, the UE needs to be paged first.

It should be noted that, steps 5B 05-5B 06 in the present application example may occur before step 5B 04.

Thereafter, if the UE initiates uplink small data transmission from the idle state, as shown in steps 5C 01-5C 02, the MME determines whether to continue to deliver the small data packet sent by the UE upwards according to whether the SCEF connection is successfully established.

Application example two

Fig. 6 is a flowchart of a connection establishment method for small data transmission according to the second application example of the present invention, and AS shown in fig. 6, the SCEF of the present invention determines whether to allow the MME to create the SCEF connection or notify the MME to create the SCEF connection according to the SCS/AS information.

As shown in fig. 6, the present application example includes the following processing steps:

6A 01-6A 06, as shown in steps 5A 01-5A 06 of FIG. 5, the UE attaches to the network, and the SCEF rejects the SCEF connection establishment request initiated by the MME according to the SCS information.

6B 01-6B 06, the SCEF sends a data transmission authorization request to the HSS, and the HSS triggers the MME to initiate the connection establishment of the SCEF according to the request. In particular, the amount of the solvent to be used,

6B01, SCS/AS sends data transmission configuration request to SCEF;

6B02, the SCEF sending a data transfer authorization request to the HSS;

6B03, the HSS sends a subscription data downloading request message to the MME, and APN configuration information is carried in UE subscription data to establish SCEF connection;

in this step, only after the HSS successfully authorizes the SCEF, the HSS sends the UE subscription data to the MME, which carries the APN configuration information, to establish the SCEF connection.

6B04, the MME sends a subscription data download response message to the HSS;

6B05, the HSS performs authorization check on the SCEF and returns a data transmission authorization response;

6B06, after receiving the data transmission authorization response, the SCEF returns a data transmission configuration response to the SCS/AS;

6B06, the MME sends an SCEF connection establishment request message to the SCEF;

6B08, the SCEF agrees to the SCEF connection establishment request, and sends a SCEF connection establishment response message to the MME.

6B09, the MME sends a bearer establishment notification to the UE, carrying information of the SCEF connection that has been established. If the UE is currently in an IDLE state, the UE needs to be paged first.

The steps 6B 07-6B 08 of the present application example may occur after step 6B03 or after step 6B 04.

Thereafter, if the UE initiates uplink small data transmission from the idle state, as shown in steps 6C 01-6C 02, the MME determines whether to continue to deliver the small data packet sent by the UE upwards according to whether the SCEF connection is successfully established.

Fig. 7 is a schematic structural diagram of an SCEF entity according to an embodiment of the present invention, and as shown in fig. 7, the SCEF entity according to the embodiment of the present invention includes a receiving unit 70, a checking unit 71, and a first connection establishing unit 72, where:

a receiving unit 70, configured to receive an SCEF connection establishment request sent by a mobility management unit MME;

a checking unit 71 for checking the third party service apparatus information;

a first connection establishing unit 72, configured to reject the SCEF connection establishment request according to the check result of the third-party service device information.

In this embodiment of the present invention, the checking unit 71 is further configured to check whether there is a data transmission configuration request of the third-party service device corresponding to the current data transmission configuration request;

correspondingly, the first connection establishing unit 72 is further configured to reject the SCEF connection establishment request when it is determined that there is no data transmission configuration request of the corresponding third-party service device.

On the basis of the SCEF entity shown in fig. 7, the SCEF entity of the embodiment of the present invention further includes:

a first sending unit (not shown in fig. 7) configured to send an SCEF connection setup response to the MME; the SCEF connection establishment response carries non-IP data connection state information.

It should be understood by those skilled in the art that the first sending unit is configured to optimize the technical solution of the SCEF entity of the embodiment of the present invention, and is not a necessary component of the SCEF entity for implementing the embodiment of the present invention.

The non-IP data connection status information of the embodiment of the present invention includes:

a second transmission unit (not shown in fig. 7) and a third transmission unit (not shown in fig. 7), wherein:

the receiving unit 70 is further configured to receive a data transmission configuration request sent by the third-party service device, and correspondingly, the second sending unit is configured to send a data transmission authorization request to a home subscriber server HSS;

the receiving unit 70 is further configured to receive a data transmission authorization response sent by the HSS, where the data transmission authorization response carries service node information;

Those skilled in the art should understand that the second sending unit and the third sending unit are configured to optimize the technical solution of the SCEF entity of the embodiment of the present invention, and are not necessarily configured to implement the SCEF entity of the embodiment of the present invention.

As another configuration, on the basis of the SCEF entity shown in fig. 7, the SCEF entity according to the embodiment of the present invention may further include: a fourth transmitting unit (not shown in fig. 7) and a second connection establishing unit (not shown in fig. 7), wherein:

the receiving unit 70 is further configured to receive a data transmission configuration request sent by the third-party service device, and correspondingly, the fourth sending unit is configured to send a data transmission authorization request to a home subscriber server HSS, so that the HSS sends subscription data information to the MME, where the subscription data information includes configuration information of an access point name APN used for establishing a SCEF connection; and the MME sends an SCEF connection establishment request to the SCEF according to the configuration information of the APN;

It should be understood by those skilled in the art that the fourth sending unit and the second connection establishing unit are configured to optimize the technical solution of the SCEF entity of the embodiment of the present invention, and are not necessarily configured to implement the SCEF entity of the embodiment of the present invention.

Those skilled in the art should understand that the implementation functions of the units in the SCEF entity shown in fig. 7 can be understood by referring to the related descriptions of the foregoing embodiments and application examples of the connection establishment method for small data transmission. The receiving unit and the sending unit can be realized through corresponding network interfaces, such as wired interfaces. The checking unit and the connection establishing unit can be formed by a microprocessor, a large programmable array FPGA or corresponding chips.

Fig. 8 is a schematic structural diagram of an MME according to a first embodiment of the present invention, and as shown in fig. 8, the MME according to the first embodiment of the present invention includes: a first sending unit 80, a first receiving unit 81, a second receiving unit 82 and a connection establishing unit 83, wherein:

a first sending unit 80, configured to send an SCEF connection establishment request to an SCEF entity with a service capability openness function;

a first receiving unit 81, configured to receive an SCEF connection establishment response sent by the SCEF entity; the SCEF connection establishment response carries non-IP data connection state information;

a second receiving unit 82, configured to receive a connection establishment request sent by the SCE;

a connection establishing unit 83, configured to establish an SCEF connection according to the SCEF connection establishing request.

Those skilled in the art should understand that the implementation functions of each unit in the MME shown in fig. 8 can be understood by referring to the related description of each embodiment and application example of the foregoing connection establishment method for small data transmission. The receiving unit and the sending unit can be realized through corresponding network interfaces, such as wired interfaces. The connection establishing unit can be formed by a microprocessor, a large programmable array FPGA or a corresponding chip.

Fig. 9 is a schematic structural diagram of an MME according to a second embodiment of the present invention, and as shown in fig. 9, the MME according to the second embodiment of the present invention includes: a first transmitting unit 90, a first receiving unit 91 and a second transmitting unit 92, wherein:

a first sending unit 90, configured to send an SCEF connection establishment request to an SCEF entity with a service capability openness function;

a first receiving unit 91, configured to receive subscription data information sent by a home subscriber server HSS, where the subscription data information includes configuration information of an access point name APN used for establishing an SCEF connection;

a second sending unit 92, configured to send an SCEF connection establishment request to an SCEF according to the configuration information of the APN.

Those skilled in the art should understand that the implementation functions of each unit in the MME shown in fig. 9 can be understood by referring to the related description of each embodiment and application example of the foregoing connection establishment method for small data transmission. The receiving unit and the sending unit can be realized through corresponding network interfaces, such as wired interfaces.

The technical schemes described in the embodiments of the present invention can be combined arbitrarily without conflict.

In the embodiments provided in the present invention, it should be understood that the disclosed method and intelligent device may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all the functional units in the embodiments of the present invention may be integrated into one second processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention.

Claims

1. A connection establishment method for small data transmission, the method comprising:

after receiving a SCEF connection establishment request sent by a mobility management unit MME, a service capability opening function SCEF entity checks the information of third-party service equipment, and rejects the SCEF connection establishment request according to the check result of the information of the third-party service equipment;

2. The connection establishment method for small data transmission according to claim 1, wherein the checking the third party service device information comprises:

3. The connection setup method for small data transmission according to claim 1, wherein the non-IP data connection status information comprises:

4. The connection setup method for small data transfer according to claim 1, wherein after rejecting the SCEF connection setup request, the method further comprises:

5. The connection setup method for small data transfer according to claim 1, wherein after rejecting the SCEF connection setup request, the method further comprises:

6. A service capability exposure function, SCEF, entity, the entity comprising: a receiving unit, a checking unit and a first connection establishing unit, wherein:

a checking unit for checking the third party service device information;

a first connection establishing unit, configured to reject the SCEF connection establishment request according to a check result of the third-party service device information;

the SCEF entity further comprises:

7. The SCEF entity according to claim 6, wherein the checking unit is further configured to check whether there is a data transmission configuration request of the third party service device currently corresponding to the SCEF entity;

8. The SCEF entity of claim 6, wherein the non-IP data connection status information includes:

9. The SCEF entity of claim 6, further comprising: a second transmission unit and a third transmission unit, wherein:

10. The SCEF entity of claim 6, further comprising: a fourth sending unit and a second connection establishing unit, wherein:

11. A mobility management unit, characterized in that the mobility management unit comprises: a first sending unit, a first receiving unit, a second receiving unit and a connection establishing unit, wherein:

a second receiving unit, configured to receive a connection establishment request sent by the SCEF;

12. A mobility management unit, characterized in that the mobility management unit comprises: a first transmitting unit, a first receiving unit and a second transmitting unit, wherein: