WO2017202305A1 - 一种小数据传输的连接管理方法、scef实体、mme及ue - Google Patents

一种小数据传输的连接管理方法、scef实体、mme及ue Download PDF

Info

Publication number
WO2017202305A1
WO2017202305A1 PCT/CN2017/085534 CN2017085534W WO2017202305A1 WO 2017202305 A1 WO2017202305 A1 WO 2017202305A1 CN 2017085534 W CN2017085534 W CN 2017085534W WO 2017202305 A1 WO2017202305 A1 WO 2017202305A1
Authority
WO
WIPO (PCT)
Prior art keywords
scef
data transmission
connection
mme
data
Prior art date
Application number
PCT/CN2017/085534
Other languages
English (en)
French (fr)
Inventor
李志军
黄梅青
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017202305A1 publication Critical patent/WO2017202305A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present invention relates to a non-IP data connection management technology, and more particularly to a connection management method for a small data transmission, a Service Capability Exposure Function (SCEF) entity, a Mobility Management Entity (MME), and a user equipment.
  • SCEF Service Capability Exposure Function
  • MME Mobility Management Entity
  • UE User Equipment
  • EPS Evolved Packet System
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT UE Narrow Band IoT UE
  • IDLE idle state
  • CONNECTED connected state
  • the large number of accesses of such NB-IoT UEs can easily lead to excessive network signaling load, causing network congestion and low revenue to operators.
  • the data transmitted by the narrow bandwidth Internet of Things (NB-IoT UE) may be non-IP, and the design of the data transmission link in the existing EPS is based on IP transmission, how to transmit non-IP data, The traditional EPS network is challenged.
  • 3GPP has enhanced the existing EPS architecture and simplified the access process of narrow bandwidth Internet of Things terminals (NB-IoT UE) so that EPS can adapt to NB-IoT UE. Access and data transfer.
  • NB-IoT UE narrow bandwidth Internet of Things terminals
  • Figure 1 shows the enhancement of the existing EPS system for narrow bandwidth IoT terminal access, including the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and the evolved packet core. Net (EPC, Evolved Packet Core) two parts.
  • EPC Evolved Packet Core
  • a base station (eNodeB, Evolved NodeB) is included.
  • the EPC packet core network includes a Home Subscriber Server (HSS), a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a Packet Data Network Gateway (P).
  • HSS Home Subscriber Server
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Gateway Packet Data Network Gateway
  • HSS Home Subscriber Server
  • Mobility management unit is the location where the user subscription data is stored in the current network, responsible for terminal-to-network non-access stratum (NAS, Non-Access Stratum) signaling management, user idle mode tracking and paging management functions and bearers. management;
  • NAS terminal-to-network non-access stratum
  • S-GW Serving Gateway
  • S-GW Serving Gateway
  • Packet Data Network Gateway It is an evolved packet domain system (EPS) and a gateway of the external network of the system, and is responsible for functions such as IP address allocation, charging function, packet filtering, and policy application of the terminal.
  • EPS evolved packet domain system
  • SCEF Service Capability Exposure Function
  • the SCEF also commonly referred to as a capability open platform, is used to establish a T6 connection (also referred to as a SCEF connection) dedicated to transmitting non-IP data between the MME and the SCEF in order to receive from the MME the UE carrying the non-NAS signaling.
  • the IP packet is sent to a third-party service platform (SCS, Service Capability Server) or a third-party application server (AS, Application Server), or receives non-IP small data packets from the SCS/AS and sends them to the MME.
  • SCS Service Capability Server
  • AS Application Server
  • FIG. 2 is a schematic flowchart of attaching a NB-IoT UE to a network and implementing non-IP data transmission based on the architecture of FIG. 1, having the following steps:
  • the UE attaches to the network and establishes a connection for transmitting non-IP data.
  • the UE initiates an attach request to the MME.
  • the MME sends a location update request to the HSS
  • the HSS returns a location update response to the MME, where the message carries the UE subscription data;
  • the subscription data includes at least one specific Access Point Name (APN) configuration for the MME to establish a PDN connection to the SCEF, and the SCEF connection can be used to transmit non-IP small data.
  • APN Access Point Name
  • the SCEF connection can be used to transmit non-IP small data.
  • it can also be used to transfer IP small data.
  • the APN configuration includes: a connection type indication, a SCEF identifier (SCEF ID), and the like.
  • a connection type indication indicates whether the APN is used to establish a connection oriented to SCEF or a connection to a PGW.
  • the SCEF identifier can be used to derive the IP address of the SCEF, which is usually the full domain name of the SCEF, and the full domain name can uniquely identify a SCEF.
  • the MME initiates a SCEF connection establishment request to the SCEF, where the APN name and an EPS bearer ID are included.
  • the MME obtains the SCEF address according to the APN configuration in the UE subscription data, and sends a SCEF connection establishment request to the SCEF. If there are multiple APNs configured in the UE subscription data to establish a SCEF connection, the MME configures a corresponding SCEF connection for the UE for each APN.
  • the SCEF receives the SCEF connection establishment request of the MME, establishes a SCEF connection for the UE, and returns a SCEF connection establishment response to the MME.
  • the MME returns an attach response to the UE
  • the MME In the attach response, the MME returns the CIOT capability supported by the network, such as whether the network supports control, optimizes the transmission mode, supports the user plane optimization transmission mode, and the like.
  • the information about the SCEF connection established for the UE such as an IP address, EPS bearer logo, and so on.
  • the UE enters an idle state.
  • the SCS/AS initiates a non-IP data transmission configuration process to the network. specifically,
  • the SCS/AS sends a non-IP data transmission configuration request to the SCEF, where the request includes an SCS identifier (SCS-ID) and an SCS reference number (SCS-Reference-ID);
  • the SCEF After receiving the non-IP data transmission configuration request of the SCS/AS, the SCEF saves the SCS identifier and the SCS reference number locally. After the UE initiates uplink small data transmission, the SCEF uses this information to send small data to the correct SCS/AS.
  • the SCEF sends a data transmission authorization request to the HSS, where the request includes a SCEF identifier (SCEF-ID) and an APN name;
  • SCEF-ID SCEF identifier
  • APN name APN name
  • the HSS performs an authorization check on the SCEF, and returns a data transmission authorization response;
  • the HSS 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 SCEF identifiers provided by the SCEF are inconsistent with the APN and SCEF identifiers in the APN configuration, the authorization check fails and the HSS returns a failure response.
  • the SCEF after receiving the data transmission authorization response, the SCEF returns a data transmission configuration response to the SCS/AS.
  • the UE initiates an uplink small data transmission process.
  • the UE initiates an RRC connection request from the idle state to the eNodeB;
  • the UE carries the NAS data packet in the RRC connection message
  • the NAS data packet carries the uplink small data packet to be sent by the UE
  • the small data packet may be a non-IP small data packet or an IP small data packet.
  • the NAS data packet includes an EPS bearer identifier corresponding to the EPS bearer used by the UE to send the uplink small data packet. Using the bearer identifier, the MME will forward the small data packet sent by the UE to the correct SCEF.
  • the eNodeB initiates an uplink NAS data transmission request to the MME, where the eNodeB carries the request The NAS packet in the step;
  • the MME receives the uplink NAS data transmission request sent by the eNodeB, and sends an originating data transmission message to the SCEF, and carries the small data packet sent by the UE;
  • the MME After receiving the message of the eNodeB, the MME extracts the small data packet to be sent by the UE from the NAS data packet, encapsulates it in the originating data transmission message, and sends it to the SCEF.
  • the MME sends an originating data transmission request to the SCEF according to the SCEF connection established in the foregoing step.
  • the SCEF after receiving the initial data transmission request sent by the MME, the SCEF initiates a data transmission request to the SCS/AS on the external API interface, and carries the small data packet sent by the UE;
  • the SCS/AS returns a data transmission response to the SCEF, which 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;
  • the SCEF returns an originating data transmission response to the MME, which may carry a small data packet to be sent by the SCS/AS to the UE;
  • the MME returns an uplink NAS data transmission response to the eNodeB, where the eNB may carry a NAS data packet to carry a small data packet to be sent to the UE;
  • the eNodeB returns an RRC connection response to the UE, and the possible NAS data packet is used to carry a small data packet to be sent to the UE;
  • the MME when the UE is attached to the network, the MME establishes a SCEF connection for the UE only according to the APN configuration in the UE subscription data.
  • the SCEF may not have received the data transmission configuration message sent by the SCS/AS before the UE wants to send the uplink fractional packet. That is to say, even if the UE initiates the originating 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 drop the uplink small data packet sent by the UE, or temporarily cache for a period of time.
  • the UE For the UE, if the UE wants the SCS/AS to send the uplink small data packet to the UE. In response, the SCS/AS is expected to return downlink small data packets. When the downlink small data returned by the SCS/AS is not received, the UE may attempt to send uplink small data multiple times. However, such an attempt will inevitably fail, resulting in a network. Waste of signaling.
  • the embodiment of the present invention provides a connection management method for small data transmission, an SCEF entity, an MME, and a UE.
  • the service capability open function SCEF entity After receiving the initial data transmission request sent by the mobility management unit MME, or receiving the data transmission configuration request sent by the third-party service device, the service capability open function SCEF entity sends non-IP data connection state information to the MME; the MME The state of the SCEF connection is set locally according to the non-IP data connection state information.
  • the SCEF entity after receiving the initial data transmission request sent by the MME, the SCEF entity sends non-IP data connection status information to the MME, including:
  • the SCEF receives an initial data transmission request sent by the MME, where the initial data transmission request carries an uplink small data packet sent by the UE;
  • the non-IP data connection status information includes:
  • the non-IP data transfer configuration is not performed, or the SCEF connection is not available.
  • the MME sets the state of the SCEF connection locally, including:
  • the MME sets the SCEF connection state locally: the SCEF connection is unavailable, or the SCEF connection is not activated.
  • the SCEF after receiving the data transmission configuration request sent by the third-party service device, the SCEF sends the non-IP data connection state information to the MME, including:
  • the SCEF After receiving the data transmission configuration request by the third party service device, the SCEF sends a data transmission authorization request to the home subscriber server HSS;
  • the HSS sends a subscription data download request to the MME, where the subscription data includes a non-IP data connection status.
  • the SCEF after receiving the data transmission configuration request sent by the third-party service device, the SCEF sends the non-IP data connection state information to the MME, including:
  • the SCEF After receiving the data transmission configuration request by the third party service device, the SCEF sends a data transmission authorization request to the home subscriber server HSS;
  • the non-IP data connection status information includes:
  • a non-IP data transfer configuration has been performed, or a SCEF connection is available.
  • the MME sets the state of the SCEF connection locally, including:
  • the MME sets the state of the SCEF connection locally: the SCEF connection is available, or the SCEF connection is activated.
  • the MME sets the state of the SCEF connection locally, including:
  • the MME sets the state of the SCEF connection locally: the SCEF connection is unavailable, or the SCEF connection is not activated.
  • the method further includes:
  • the MME After receiving the NAS data transmission request sent by the UE, the MME sends a message rejecting the NAS data transmission request to the UE, where the rejection message carries an indication of a failure reason; the indication of the failure reason includes: the SCEF connection is unavailable, Or the SCEF connection is not activated.
  • the MME when the MME sends a message rejecting the NAS data transmission request to the UE, the information about the delay time is also sent.
  • the method further includes:
  • the UE After receiving the failure reason indication sent by the MME, the UE does not attempt to initiate an uplink small data transmission request within a configuration time or a delay time according to the time configured by the UE or according to the delay time information sent by the MME. .
  • the SCEF entity provided by the embodiment of the present invention includes: a first receiving unit and a first sending unit, where:
  • the first receiving unit is configured to receive an initial data transmission request sent by the mobility management unit MME, or receive a data transmission configuration request sent by the third-party service device;
  • the first sending unit is configured to send non-IP data connection state information to the MME, so that the MME locally sets the state of the SCEF connection according to the non-IP data connection state information.
  • the SCEF entity further includes: an checking unit and a second sending unit;
  • the first receiving unit is further configured to receive an initial data transmission request sent by the MME, where the initial data transmission request carries an uplink small data packet sent by the UE;
  • the checking unit is configured to check the information of the third-party service device, and trigger the second sending unit when determining that there is no corresponding information of the third-party service device;
  • the second sending unit is configured to send an originating data transmission response message to the MME, where the response message carries non-IP data connection status information.
  • the non-IP data connection status information includes:
  • the non-IP data transfer configuration is not performed, or the SCEF connection is not available.
  • the SCEF entity further includes: a third sending unit;
  • the first receiving unit is further configured to receive the third-party service device to send a data transmission configuration request, and trigger the third sending unit;
  • a third sending unit configured to send a data transmission authorization request to the home subscriber server HSS, so that the HSS sends a subscription data download request to the MME, where the subscription data includes Non-IP data connection status.
  • the SCEF entity further includes: a fourth sending unit, a second receiving unit, and a fifth sending unit;
  • the first receiving unit is further configured to receive the third-party service device to send a data transmission configuration request, and trigger the fourth sending unit;
  • a fourth sending unit configured to send a data transmission authorization request to the home subscriber server HSS;
  • the second receiving unit is configured to trigger the fifth sending unit after receiving the data transmission authorization response sent by the HSS;
  • the fifth sending unit is configured to send a non-IP data connection state to the MME.
  • the non-IP data connection status information includes:
  • a non-IP data transfer configuration has been performed, or a SCEF connection is available.
  • the mobility management unit provided by the embodiment of the present invention includes: a first receiving unit and a setting unit, where:
  • a first receiving unit configured to receive non-IP data connection state information sent by a service capability open function SCEF entity;
  • the setting unit is configured to locally set the state of the SCEF connection according to the non-IP data connection state information.
  • the first receiving unit includes: a first receiving subunit, a first sending subunit, and a second receiving subunit, where:
  • the first receiving subunit is configured to receive an uplink small data packet that is sent by the user equipment UE and that is included in the non-access stratum NAS, and trigger the first sending subunit;
  • a first sending subunit configured to send an originating data transmission request to the SCEF entity, where the initial data transmission request carries the uplink small data packet;
  • the second receiving subunit is configured to receive an initial data transmission response message sent by the SCEF entity, where the response message carries non-IP data connection status information.
  • the mobility management unit further includes:
  • the second receiving unit is configured to receive a subscription data download request sent by the home subscriber server HSS, where the subscription data includes a non-IP data connection state.
  • the non-IP data connection status information includes:
  • Non-IP data transfer configuration has been performed, or SCEF connection is available
  • the setting unit is further configured to set the state of the SCEF connection locally, the SCEF connection is available, or the SCEF connection is activated.
  • the mobility management unit further includes: a fourth receiving unit and a sending unit;
  • the setting unit is further configured to: when the non-IP data connection state information includes that the non-IP data transmission configuration is not performed, or the SCEF connection is unavailable, the state of the SCEF connection is locally set to be unavailable for the SCEF connection, or the SCEF connection is not activated. ;
  • the fourth receiving unit is further configured to receive the NAS data transmission request sent by the UE, and trigger the sending unit;
  • the sending unit is configured to send a message to the UE rejecting the NAS data transmission request, where the rejection message carries an indication of the reason for the failure.
  • the indication of the reason for the failure includes: the SCEF connection is unavailable, or the SCEF connection is not activated.
  • the sending unit when the sending unit sends a message rejecting the NAS data transmission request to the UE, the sending unit further sends the information of the delay time.
  • the user equipment includes: a sending unit, a receiving unit, and a requesting unit, where:
  • a sending unit configured to send a non-access stratum NAS data transmission request to the mobility management unit MME, where the uplink small data packet is included in the NAS;
  • a receiving unit configured to receive a message that is rejected by the MME and rejects a NAS data transmission request, where the rejection message carries a failure cause indication, or a failure reason indication, and a delay time;
  • the requesting unit is configured to no longer attempt to initiate an uplink small data transmission request within a configuration time or a delay time of the user equipment.
  • a computer storage medium is further provided, and the computer storage medium may store an execution instruction for implementing the connection management method for small data transmission in the above embodiment.
  • connection management method for small data transmission the SCEF entity, the MME, the UE, the SCEF entity after receiving the initial data transmission request sent by the MME, or receiving the data transmission configuration request sent by the third party service device, such as the SCS/AS, in the embodiment of the present invention And transmitting non-IP data connection status information to the MME, so that the MME locally sets the state of the SCEF connection in the MME according to the non-IP data connection status information.
  • the technical solution of the embodiment of the present invention enables the network side to manage the establishment and use of the SCEF connection, and prevents the terminal from initiating uplink small data transmission and cannot correctly send to the SCS/AS, and can further notify the terminal that the current SCEF connection is temporarily unavailable. Therefore, the UE does not have to try to send uplink small data multiple times, thereby avoiding waste of network signaling.
  • FIG. 1 is a schematic structural diagram of an enhanced EPS system
  • FIG. 2 is a schematic flowchart of implementing non-IP data transmission by a UE based on the network architecture shown in FIG. 1 attached to a network;
  • FIG. 3 is a flowchart of a method for managing connection of small data transmission according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a connection establishment method for small data transmission according to application example 2 of the present invention.
  • FIG. 6 is a schematic structural diagram of a structure of a SCEF entity according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a structure of an MME according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a structure of a UE according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for managing connection of small data transmission according to an embodiment of the present invention. As shown in FIG. 3, a connection management method for small data transmission according to an embodiment of the present invention includes the following processing steps:
  • Step 301 After receiving the initial data transmission request sent by the mobility management unit MME, or receiving the data transmission configuration request sent by the third-party service device, the SCEF entity sends non-IP data connection state information to the MME.
  • the third-party service device includes a network element device such as a third-party service platform (SCS) or a third-party application server (AS, Application Server).
  • SCS third-party service platform
  • AS Application Server
  • Step 302 The MME locally sets the state of the SCEF connection according to the non-IP data connection state information.
  • the SCEF entity after receiving the initial data transmission request sent by the MME, the SCEF entity sends non-IP data connection state information to the MME, which specifically includes:
  • the SCEF receives an initial data transmission request sent by the MME, where the initial data transmission request carries an uplink small data packet sent by the UE;
  • the information of the third-party service device is checked, and when it is determined that there is no corresponding information of the third-party service device, an originating data transmission response message is sent to the MME, where the response message carries non-IP data connection status information.
  • the above non-IP data connection status information includes: the non-IP data transmission configuration is not performed, or the SCEF connection is unavailable.
  • the MME sets the state of the SCEF connection locally, including: the MME setting the SCEF connection state locally: the SCEF connection is unavailable, or the SCEF connection is not activated.
  • the SCEF after receiving the data transmission configuration request sent by the third-party service device, the SCEF sends the non-IP data connection state information to the MME, including:
  • the SCEF After receiving the data transmission configuration request, the SCEF sends a data transmission authorization request to the home subscriber server HSS, so that the HSS sends a subscription data download request to the MME, where the subscription data includes non-IP data. Connection Status.
  • the SCS sends a data transmission configuration request to the SCEF;
  • the SCEF sends a data transmission authorization request to the HSS
  • the HSS sends a subscription data download request to the MME, and includes a non-IP data connection status in the subscription data;
  • the MME sets the SCEF connection state locally according to the non-IP data connection status sent by the HSS.
  • the SCEF may send the non-IP data connection status information to the MME, and may further include:
  • the SCEF After receiving the data transmission configuration request by the third party service device, the SCEF sends a data transmission authorization request to the home subscriber server HSS;
  • the SCS/AS sends a data transmission configuration request to the SCEF;
  • the SCEF sends a data transmission authorization request to the HSS, and receives a data transmission authorization response from the HSS;
  • the SCEF sends a non-IP data connection status to the MME.
  • the MME sets the SCEF connection state locally according to the non-IP data connection status sent by the SCEF.
  • the above non-IP data connection status information includes: a non-IP data transmission configuration has been performed, or an SCEF connection is available.
  • the MME sets the state of the SCEF connection locally, including:
  • the MME sets the state of the SCEF connection locally: the SCEF connection is available, or the SCEF connection is activated.
  • the embodiment of the present invention when the non-IP data connection status information includes that the non-IP data transmission configuration is not performed, or the SCEF connection is unavailable, the embodiment of the present invention may further include the following steps:
  • the MME After receiving the NAS data transmission request sent by the UE, the MME sends a message rejecting the NAS data transmission request to the UE, where the rejection message carries an indication of the reason for the failure.
  • the indication of the reason for the failure includes: the SCEF connection is unavailable, or the SCEF connection is not activated.
  • the MME when the MME sends a message rejecting the NAS data transmission request to the UE, the MME may also send back-off time information.
  • the UE after receiving the indication of the failure reason sent by the MME, the UE does not try again according to the time configured by the UE or according to the information of the delay time sent by the MME in the configuration time or delay time. Initiate an upstream small data transmission request.
  • SCEF 4 is a SCEF of the present invention returns a non-IP data connection state to the MME, and the MME sets the SCEF connection state accordingly, and determines whether to receive the uplink small data transmission initiated by the UE according to the SCEF connection state.
  • connection management method for small data transmission in this application example includes the following processing steps:
  • the MME sets the SCEF connection state according to the non-IP data connection status returned by the SCEF.
  • the UE is attached to the network, and the network creates a SCEF connection for it, and then the UE enters an idle state.
  • 2A01 ⁇ 2A07;
  • the UE initiates an RRC connection request from the idle state to the eNodeB, and carries the NAS data packet, where the NAS data packet carries the uplink small data packet to be sent by the UE;
  • the eNodeB initiates an uplink NAS data transmission request to the MME, where the NAS data packet in the foregoing step is carried;
  • the MME receives the uplink NAS data transmission request sent by the eNodeB, and sends an originating data transmission message to the SCEF, carrying the small data packet sent by the UE;
  • SCEF determines whether to reject the originating data transmission of the MME according to the SCS information. begging;
  • the SCEF checks the SCS information, that is, checks whether the SCEF connection has corresponding SCS information, that is, checks whether the SCS requests the non-IP data transmission configuration flow.
  • the uplink NAS data transmission request sent by the MME is rejected.
  • the SCEF returns an originating data transmission response to the MME, where the non-IP data connection state is carried;
  • the non-IP data connection status may be: the non-IP data transmission configuration is not performed, or the SCEF connection is unavailable.
  • the non-IP data connection status can be represented by a failure cause.
  • the MME sets the SCEF connection status according to the initial data transmission response returned by the SCEF;
  • the SCEF is in the non-IP data connection state carried in the initial data transmission response. If the indication is: the non-IP data transmission configuration is not performed, or the SCEF connection is unavailable, the MME locally sets the corresponding SCEF connection status to "SCEF is not available" or "SCEF connection is not activated” status.
  • the MME returns an uplink NAS data transmission response to the eNodeB, and carries the failure reason;
  • the reason for the failure returned by the MME may be: the SCEF connection is unavailable, or the SCEF connection is not activated.
  • the UE may not initiate an uplink small data transmission process within a certain period of time (the time is set by the UE itself).
  • the MME may also carry a back-off time, which indicates that the UE should not attempt to initiate an uplink small data transmission process within the delay time.
  • the eNodeB returns an RRC connection response to the UE, and carries the failure reason carried by the MME in the foregoing step;
  • the SCS/AS sends a data transmission configuration request to the SCEF, and the SCEF according to the The request triggers the MME to set the SCEF connection status.
  • the SCS/AS sends a data transmission configuration request to the SCEF;
  • the SCEF sends a data transmission authorization request to the HSS
  • the HSS performs an authorization check on the SCEF, and returns a data transmission authorization response;
  • the SCEF after receiving the data transmission authorization response, the SCEF returns a data transmission configuration response to the SCS/AS;
  • the SCEF sends a notification request message to the MME, and carries a non-IP data connection state;
  • the non-IP data connection status may be: a non-IP data transmission configuration has been performed, or a SCEF connection is available.
  • the MME sets the SCEF connection state locally according to the notification request message sent by the SCEF, and sets the status as "SCEF connection is available” or "SCEF connection is activated”;
  • the MME sends a notification response message to the SCEF.
  • steps 4B05 to 4B07 may occur before step 4B04. Thereafter, if the UE initiates uplink small data transmission from the idle state, as in steps 4C01 to 4C02, the MME determines whether to continue to deliver the small data packet sent by the UE according to the SCEF connection state.
  • the HSS sends a subscription data download to the MME, and the MME sets the SCEF connection status according to the HSS message, and determines whether to receive the uplink small data transmission initiated by the UE according to the SCEF connection status.
  • connection management method for small data transmission in this application example includes the following processing steps:
  • the HSS sends the subscription data to the MME according to the data transmission authorization request sent by the SCEF, and triggers the MME to set the SCEF connection status.
  • the SCS/AS sends a data transmission configuration request to the SCEF;
  • the SCEF sends a data transmission authorization request to the HSS
  • the HSS sends a subscription data download request message to the MME, and carries the non-IP data connection status in the UE subscription data;
  • Non-IP data connection status which can be: non-IP data transmission configuration has been performed, or SCEF connection is available.
  • the non-IP data connection status may be included in the APN configuration information.
  • the MME sets the SCEF connection status locally according to the subscription data delivered by the HSS, and sets the status as "SCEF connection is available” or "SCEF connection is activated”;
  • the MME sends a subscription data download response message to the HSS;
  • the HSS performs an authorization check on the SCEF, and returns a data transmission authorization response;
  • the SCEF after receiving the data transmission authorization response, the SCEF returns a data transmission configuration response to the SCS/AS;
  • the MME determines whether to continue to deliver the small data packet sent by the UE according to the SCEF connection state.
  • FIG. 6 is a schematic structural diagram of a structure of a SCEF entity according to an embodiment of the present invention.
  • the SCEF entity in the embodiment of the present invention includes a first receiving unit 60 and a first sending unit 61, where:
  • the first receiving unit 60 is configured to receive an initial data transmission request sent by the mobility management unit MME, or receive a data transmission configuration request sent by the third-party service device;
  • the first sending unit 61 is configured to send non-IP data connection state information to the MME, so that the MME locally sets the state of the SCEF connection according to the non-IP data connection state information.
  • the SCEF entity of the embodiment of the present invention may further include: an inspection unit (not shown in FIG. 6) and a second transmission unit (not shown in FIG. 6); in,
  • the first receiving unit 60 is further configured to receive an initial data transmission request sent by the MME, where the initial data transmission request carries an uplink small data packet sent by the UE;
  • the checking unit is configured to check the information of the third-party service device, and trigger the second sending unit when determining that there is no corresponding information of the third-party service device;
  • the second sending unit is configured to send an originating data transmission response message to the MME, where the response message carries non-IP data connection status information.
  • the non-IP data connection status information includes:
  • the non-IP data transfer configuration is not performed, or the SCEF connection is not available.
  • the SCEF entity in the embodiment of the present invention may further include: a third sending unit (not shown in FIG. 6);
  • the first receiving unit 60 is further configured to receive the third-party service device to send a data transmission configuration request, and trigger the third sending unit;
  • the third sending unit is configured to send a data transmission authorization request to the home subscriber server HSS, so that the HSS sends a subscription data download request to the MME, where the subscription data includes a non-IP data connection state.
  • the SCEF entity in the embodiment of the present invention may further include: a fourth sending unit (not shown in FIG. 6) and a second receiving unit (FIG. 6). Not shown) and a fifth transmitting unit; wherein
  • the first receiving unit is further configured to receive the third-party service device to send a data transmission configuration request, and trigger the fourth sending unit;
  • a fourth sending unit configured to send a data transmission authorization request to the home subscriber server HSS;
  • the second receiving unit is configured to trigger the fifth sending unit after receiving the data transmission authorization response sent by the HSS;
  • the fifth sending unit is configured to send a non-IP data connection state to the MME.
  • the non-IP data connection status information includes:
  • a non-IP data transfer configuration has been performed, or a SCEF connection is available.
  • the receiving unit and the transmitting unit can be implemented through a corresponding network interface, such as a wired interface.
  • the inspection unit or the like can be constituted by a microprocessor, a large programmable array FPGA, or a corresponding chip.
  • FIG. 7 is a schematic structural diagram of a structure of an MME according to an embodiment of the present invention.
  • an MME according to an embodiment of the present invention includes a first receiving unit 70 and a setting unit 71, where:
  • the first receiving unit 70 is configured to receive non-IP data connection state information sent by the service capability opening function SCEF entity;
  • the setting unit 71 is configured to locally set the state of the SCEF connection according to the non-IP data connection state information.
  • the first receiving unit 70 specifically includes: a first receiving subunit (not shown in FIG. 7), a first transmitting subunit (not shown in FIG. 7), and a second receiving subunit ( Not shown in Figure 7, where:
  • the first receiving subunit is configured to receive an uplink small data packet that is sent by the user equipment UE and that is included in the non-access stratum NAS, and trigger the first sending subunit;
  • a first sending subunit configured to send an originating data transmission request to the SCEF entity, where the initial data transmission request carries the uplink small data packet;
  • the second receiving subunit is configured to receive an initial data transmission response message sent by the SCEF entity, where the response message carries non-IP data connection status information.
  • the MME in the embodiment of the present invention may further include:
  • the second receiving unit (not shown in FIG. 7) is configured to receive a subscription data download request sent by the home subscriber server HSS, where the subscription data includes a non-IP data connection status.
  • the non-IP data connection status information includes:
  • Non-IP data transfer configuration has been performed, or SCEF connection is available
  • the setting unit 71 is further configured to set the state of the SCEF connection locally, the SCEF connection is available, or the SCEF connection is activated.
  • the MME of the embodiment of the present invention may further include: a fourth receiving unit (not shown in FIG. 7) and a sending unit (not shown in FIG. 7);
  • the setting unit 71 is further configured to: when the non-IP data connection status information includes that the non-IP data transmission configuration is not performed, or the SCEF connection is unavailable, the state of the SCEF connection is locally set to be unavailable for the SCEF connection, or the SCEF connection is not activation;
  • the fourth receiving unit is further configured to receive the NAS data transmission request sent by the UE, and trigger the sending unit;
  • the sending unit is configured to send a message to the UE rejecting the NAS data transmission request, where the rejection message carries an indication of the reason for the failure.
  • the indication of the reason for the failure includes: the SCEF connection is unavailable, or the SCEF connection is not activated.
  • the sending unit when the sending unit sends a message rejecting the NAS data transmission request to the UE, the sending unit further sends the information of the delay time.
  • the receiving unit and the transmitting unit can be implemented through a corresponding network interface, such as a wired interface.
  • the setting unit or the like can be constituted by a microprocessor, a large programmable array FPGA, or a corresponding chip.
  • FIG. 8 is a schematic structural diagram of a structure of a UE according to an embodiment of the present invention.
  • the UE in the embodiment of the present invention includes a sending unit 80, a receiving unit 81, and a requesting unit 82, where:
  • the sending unit 80 is configured to send a non-access stratum NAS data transmission request to the mobility management unit MME, where the uplink small data packet is included in the NAS;
  • the receiving unit 81 is configured to receive a message for rejecting the NAS data transmission request sent by the MME, where the rejection message carries a failure cause indication, or a failure reason indication, and a delay between;
  • the requesting unit 82 is configured to no longer attempt to initiate an uplink small data transmission request during the configuration time or delay time of the user equipment.
  • the receiving unit and the transmitting unit can be implemented through a corresponding network interface, such as a wired interface.
  • the disclosed method and smart device may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one second processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • connection management method for small data transmission the SCEF entity, the MME, the UE, the SCEF entity after receiving the initial data transmission request sent by the MME, or receiving the data transmission configuration request sent by the third party service device, such as the SCS/AS, in the embodiment of the present invention And transmitting non-IP data connection status information to the MME, so that the MME locally sets the state of the SCEF connection in the MME according to the non-IP data connection status information.
  • the technical solution of the embodiment of the present invention enables the network side to manage the establishment and use of the SCEF connection, and prevents the terminal from initiating uplink small data transmission and cannot correctly send to the SCS/AS, and can further notify the terminal that the current SCEF connection is temporarily unavailable. Therefore, the UE does not have to try to send uplink small data multiple times, thereby avoiding waste of network signaling.

Abstract

本发明公开了一种小数据传输的连接管理方法、SCEF实体、MME、UE，所述方法包括：SCEF实体接收MME发送的始发数据传输请求后，或接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息，以使所述MME根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。

Description

一种小数据传输的连接管理方法、SCEF实体、MME及UE 技术领域
本发明涉及非IP数据连接管理技术，尤其涉及一种小数据传输的连接管理方法、服务能力开放功能(SCEF，Service Capability Exposure Function)实体、移动性管理单元(MME，Mobility Management Entity)、用户设备(UE，User Equipment)。
背景技术
物联网(IoT，Internet of Things)的飞速发展，给第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)定义的演进分组域系统(EPS，Evolved Packet System)带来了巨大的挑战。在应用于物联网的终端(UE，User Equipment)中，有一类典型的窄带宽物联网终端(NB-IoT UE，Narrow Band IoT UE)。窄带宽物联网终端(NB-IoT UE)接入网络时，通常发送或接收的有效数据量很小，但是为了实现从空闲态(IDLE)进入连接态(CONNECTED)发起数据，所操作的网络信令本身，远远大于所发送或接收的数据量。因此，这种NB-IoT UE的大量接入，很容易导致网络信令负荷过高，造成网络拥塞，并且对运营商所带来的收益很低。另一方面，窄带宽物联网终端(NB-IoT UE)所传输的数据，可能是非IP的，而现有EPS中数据传输链路的设计，是基于IP传输的，如何传输非IP数据，也给传统EPS网络提出了挑战。
为了适应移动物联网通讯的发展，3GPP在现有EPS的架构上进行了增强，并对窄带宽物联网终端(NB-IoT UE)的接入流程进行了简化，以便EPS能适应NB-IoT UE的接入和数据传输。
如图1所示是现有EPS系统对窄带宽物联网终端接入所进行的增强，主要包括演进的通用陆地无线接入网络(E-UTRAN，Evolved Universal Terrestrial Radio Access Network)和演进的分组核心网(EPC，Evolved  Packet Core)两部分。
在E-UTRAN无线接入网络中，包括基站(eNodeB，Evolved NodeB)。
在EPC分组核心网中，包含了归属用户数据服务器(HSS，Home Subscriber Server)、移动性管理单元(MME，Mobility Management Entity)、服务网关(S-GW，Serving Gateway)、分组数据网络网关(P-GW，PDN Gateway)，其中：
归属用户服务器(HSS，Home Subscriber Server)：是用户签约数据的永久存放地点，位于用户签约的归属网；
移动性管理单元：是用户签约数据在当前网络的存放地点，负责终端到网络的非接入层(NAS，Non-Access Stratum)信令管理、用户空闲模式下的跟踪和寻呼管理功能和承载管理；
服务网关(S-GW，Serving Gateway)：是核心网到无线系统的网关，负责终端到核心网的用户面承载、终端空闲模式下的数据缓存、网络侧发起业务请求的功能、合法窃听和分组数据路由和转发功能；
分组数据网络网关(P-GW，PDN Gateway)：是演进的分组域系统(EPS)和该系统外部网络的网关，负责终端的IP地址分配、计费功能、分组包过滤、策略应用等功能。
另外，为了支持窄带宽物联网终端的非IP数据传输，3GPP引入了服务能力开放功能(SCEF，Service Capability Exposure Function)。SCEF通常也被称为能力开放平台，被用于在MME和SCEF间建立专用于传输非IP数据的T6连接(也称为SCEF连接)，以便于从MME接收UE携带在NAS信令中的非IP小数据包并发送给第三方服务平台(SCS，Service Capability Server)或第三方应用服务器(AS，Application Server)，或从SCS/AS处接收非IP小数据包并发送给MME。
图2是在基于图1的架构下，NB-IoT UE附着到网络并实现非IP数据传输的流程示意图，具有如下步骤：
2A01～2A07，UE附着到网络，并建立用于传输非IP数据的连接。
2A01，UE向MME发起附着请求。
在附着请求中，携带UE的物联网接入能力信息，如UE是否支持控制么优化传输方式、是否支持用户面优化传输方式，等等；
2A02，MME向HSS发送位置更新请求；
2A03，HSS向MME返回位置更新响应，在该消息中携带UE签约数据；
特别地，在本例中，签约数据中包含至少一个特定的接入点名称(APN，Access Point Name)配置，用于供MME建立到SCEF的PDN连接，该SCEF连接可用于传输非IP小数据，当然，也可以用于传输IP小数据。
具体地，该APN配置包含：连接类型指示、SCEF标识(SCEF ID)等信息。连接类型指示，表明该APN用于建立面向SCEF的连接，还是面向PGW的连接。SCEF标识，可推导出该SCEF的IP地址，通常是SCEF的全域名，该全域名可以唯一地标识出一个SCEF。
2A04，MME向SCEF发起SCEF连接建立请求，其中包含APN名称，EPS承载标识(EPS Bearer ID)；
MME根据UE签约数据中的APN配置，获取SCEF地址，并向该SCEF发送SCEF连接建立请求。如果UE签约数据中有多个APN配置用来建立SCEF连接，则MME会针对每个APN配置为UE建立对应的SCEF连接。
对于每一个SCEF连接，目前仅创建一个EPS承载，即MME仅为该SCEF连接分配一个EPS承载标识。
2A05，SCEF收到MME的SCEF连接建立请求，为该UE建立SCEF连接，并向MME返回SCEF连接建立响应；
2A06，MME向UE返回附着响应；
在附着响应中，MME返回网络所支持的CIOT能力，如网络是否支持控制么优化传输方式、是否支持用户面优化传输方式，等等。
在附着响应中，还包含为UE建立的SCEF连接的信息，如：IP地址、 EPS承载标识，等等。
其后，UE进入空闲态。
2B01～2B04，SCS/AS向网络发起非IP数据传输配置过程。具体地，
2B01，SCS/AS向SCEF发送非IP数据传输配置请求，在该请求中包含SCS标识(SCS-ID)、SCS参考号(SCS-Reference-ID)；
SCEF收到SCS/AS的非IP数据传输配置请求后，在本地保存SCS标识、SCS参考号。当UE发起上行小数据传输后，SCEF使用这些信息将小数据发送给正确的SCS/AS。
2B02，SCEF向HSS发送数据传输授权请求，在该请求中包含SCEF标识(SCEF-ID)、APN名称；
2B03，HSS对SCEF进行授权检查，返回数据传输授权响应；
HSS收到数据传输授权请求后，根据APN配置中的APN、SCEF标识，对SCEF所提供的APN、SCEF标识，进行授权检查。若SCEF所提供的APN、SCEF标识和APN配置中的APN、SCEF标识不一致，则授权检查失败，HSS返回失败响应。
2B04，SCEF收到数据传输授权响应后，向SCS/AS返回数据传输配置响应；
2C01～2C08，UE发起上行小数据传输流程。
2C01，UE从空闲态，向eNodeB发起RRC连接请求；
在本例中，UE在RRC连接消息中携带NAS数据包，该NAS数据包中携带UE要发送的上行小数据包，该小数据包可以是非IP小数据包、或IP小数据包。
在该NAS数据包中，同时包含UE要发送上行小数据包所使用的EPS承载所对应的EPS承载标识。使用该承载标识，MME将可以将UE发送的该小数据包转发给正确的SCEF。
2C02，eNodeB向MME发起上行NAS数据传输请求，其中携带在前 述步骤中的NAS数据包；
2C03，MME收到eNodeB发送的上行NAS数据传输请求，向SCEF发送始发数据传输消息，携带UE发送的小数据包；
MME收到eNodeB的消息后，从NAS数据包中提取出UE要发送的小数据包，封装在始发数据传输消息中，发送给SCEF。MME根据前述步骤中建立的SCEF连接，向SCEF发送始发数据传输请求。
2C04，SCEF收到MME发送的始发数据传输请求后，在外部API接口上向SCS/AS发起数据传输请求，携带UE发送的小数据包；
2C05，SCS/AS向SCEF返回数据传输响应，其中可能携带SCS/AS要发送给UE的下行小数据包，该小数据包可能是非IP小数据包、或IP小数据包；
2C06，SCEF向MME返回始发数据传输响应，其中可能携带SCS/AS要发送给UE的小数据包；
需要明确的是，SCEF是否等候步骤2C04～2C05完成后才发起2C06步骤，完全取决于SCEF内部实现。
2C07，MME向eNodeB返回上行NAS数据传输响应，其中可能携带NAS数据包，用以携带要发往UE的小数据包；
2C08，eNodeB向UE返回RRC连接响应，可能NAS数据包，用以携带要发往UE的小数据包；
在上述流程中，在UE附着到网络时，MME仅根据UE签约数据中的APN配置，为UE建立SCEF连接。而当UE欲发送上行小数包前，SCEF可能还未收到SCS/AS发送的数据传输配置消息。也就是说，即使UE发起了始发小数据传输，该UE发送的上行小数据包，也只能发送到SCEF，而无法发送给SCS/AS。此时，SCEF有可能丢弃UE发送的上行小数据包，或暂时缓存一段时间。
而对于UE而言，如果UE希望SCS/AS对UE发送的上行小数据包 有所回应，即希望SCS/AS返回下行小数据包，在未收到SCS/AS返回的下行小数据时，UE可能多次尝试发送上行小数据，然而这种尝试必然会失败，也导致网络信令的浪费。
发明内容
为解决上述技术问题，本发明实施例提供了一种小数据传输的连接管理方法、SCEF实体、MME、UE。
本发明实施例提供的小数据传输的连接管理方法，包括：
服务能力开放功能SCEF实体接收移动性管理单元MME发送的始发数据传输请求后，或接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息；所述MME根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
本发明实施例中，所述SCEF实体接收所述MME发送的始发数据传输请求后，向所述MME发送非IP数据连接状态信息，包括：
所述SCEF接收所述MME发送的始发数据传输请求，所述始发数据传输请求中携带有UE发送的上行小数据包；
检查所述第三方服务设备的信息，在确定不存在对应的所述第三方服务设备的信息时，向所述MME发送始发数据传输响应消息，所述响应消息中携带有非IP数据连接状态信息。
本发明实施例中，所述非IP数据连接状态信息包括：
非IP数据传输配置未执行、或SCEF连接不可用。
本发明实施例中，所述MME在本地设置SCEF连接的状态，包括：
所述MME在本地设置SCEF连接状态为：SCEF连接不可用、或SCEF连接未激活。
本发明实施例中，所述SCEF接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息，包括：
所述SCEF接收所述第三方服务设备发送数据传输配置请求后，向归属用户服务器HSS发送数据传输授权请求；
所述HSS向MME发送签约数据下载请求，所述签约数据中包含非IP数据连接状态。
本发明实施例中，所述SCEF接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息，包括：
所述SCEF接收所述第三方服务设备发送数据传输配置请求后，向归属用户服务器HSS发送数据传输授权请求；
接收所述HSS发送的数据传输授权响应后，向所述MME发送非IP数据连接状态。
本发明实施例中，所述非IP数据连接状态信息包括：
非IP数据传输配置已执行、或SCEF连接可用。
本发明实施例中，所述MME在本地设置SCEF连接的状态，包括：
所述MME在本地设置SCEF连接的状态为：SCEF连接可用、或SCEF连接已激活。
本发明实施例中，所述非IP数据连接状态信息包括非IP数据传输配置未执行、或SCEF连接不可用时，所述MME在本地设置SCEF连接的状态，包括：
所述MME在本地设置SCEF连接的状态为：SCEF连接不可用、或SCEF连接未激活。
本发明实施例中，所述方法还包括：
在所述MME接收所述UE发送的NAS数据传输请求后，向UE发送拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因的指示；所述失败原因的指示包括：SCEF连接不可用、或SCEF连接未激活。
本发明实施例中，所述MME向UE发送拒绝NAS数据传输请求的消息时，还发送延迟时间的信息。
本发明实施例中，所述方法还包括：
所述UE接收所述MME发送的失败原因指示后，根据所述UE配置的时间，或根据所述MME发送的延迟时间的信息，在配置时间或延迟时间内不再尝试发起上行小数据传输请求。
本发明实施例提供的SCEF实体，所述SCEF实体包括：第一接收单元和第一发送单元，其中：
第一接收单元，设置为接收移动性管理单元MME发送的始发数据传输请求，或接收第三方服务设备发送的数据传输配置请求；
第一发送单元，设置为向所述MME发送非IP数据连接状态信息，以使所述MME根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
本发明实施例中，所述SCEF实体还包括：检查单元和第二发送单元；其中，
所述第一接收单元，还设置为接收所述MME发送的始发数据传输请求，所述始发数据传输请求中携带有UE发送的上行小数据包；
检查单元，设置为检查所述第三方服务设备的信息，在确定不存在对应的所述第三方服务设备的信息时，触发所述第二发送单元；
第二发送单元，设置为向所述MME发送始发数据传输响应消息，所述响应消息中携带有非IP数据连接状态信息。
本发明实施例中，所述非IP数据连接状态信息包括：
非IP数据传输配置未执行、或SCEF连接不可用。
本发明实施例中，所述SCEF实体还包括：第三发送单元；其中，
所述第一接收单元，还设置为接收所述第三方服务设备发送数据传输配置请求，并触发所述第三发送单元；
第三发送单元，设置为向归属用户服务器HSS发送数据传输授权请求，以使所述HSS向MME发送签约数据下载请求，所述签约数据中包含 非IP数据连接状态。
本发明实施例中，所述SCEF实体还包括：第四发送单元、第二接收单元和第五发送单元；其中，
所述第一接收单元，还设置为接收所述第三方服务设备发送数据传输配置请求，并触发所述第四发送单元；
第四发送单元，设置为向归属用户服务器HSS发送数据传输授权请求；
第二接收单元，设置为接收所述HSS发送的数据传输授权响应后，触发所述第五发送单元；
第五发送单元，设置为向所述MME发送非IP数据连接状态。
本发明实施例中，所述非IP数据连接状态信息包括：
非IP数据传输配置已执行、或SCEF连接可用。
本发明实施例提供的移动性管理单元，包括：第一接收单元和设置单元，其中：
第一接收单元，设置为接收服务能力开放功能SCEF实体发送的非IP数据连接状态信息；
设置单元，设置为根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
本发明实施例中，所述第一接收单元包括：第一接收子单元、第一发送子单元和第二接收子单元，其中：
第一接收子单元，设置为接收用户设备UE发送的包含在非接入层NAS中的上行小数据包，并触发所述第一发送子单元；
第一发送子单元，设置为向所述SCEF实体发送始发数据传输请求，所述始发数据传输请求中携带有所述上行小数据包；
第二接收子单元，设置为接收所述SCEF实体发送的始发数据传输响应消息，所述响应消息中携带有非IP数据连接状态信息。
本发明实施例中，所述移动性管理单元还包括：
第二接收单元，设置为接收归属用户服务器HSS发送的签约数据下载请求，所述签约数据中包含非IP数据连接状态。
本发明实施例中，所述非IP数据连接状态信息包括：
非IP数据传输配置已执行、或SCEF连接可用；
对应地，所述设置单元，还设置为在本地设置SCEF连接的状态为，SCEF连接可用、或SCEF连接已激活。
本发明实施例中，所述移动性管理单元还包括：第四接收单元和发送单元；
所述设置单元，还设置为在所述非IP数据连接状态信息包括非IP数据传输配置未执行、或SCEF连接不可用时，在本地设置SCEF连接的状态为SCEF连接不可用、或SCEF连接未激活；
对应地，第四接收单元，还设置为接收所述UE发送的NAS数据传输请求，并触发所述发送单元；
发送单元，设置为向UE发送拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因的指示。
本发明实施例中，所述失败原因的指示包括：SCEF连接不可用、或SCEF连接未激活。
本发明实施例中，所述发送单元在向UE发送拒绝NAS数据传输请求的消息时，还发送延迟时间的信息。
本发明实施例提供的用户设备，包括：发送单元、接收单元和请求单元，其中：
发送单元，设置为向移动性管理单元MME发送非接入层NAS数据传输请求，其中，在NAS中包含上行小数据包；
接收单元，设置为接收所述MME发送的拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因指示、或者失败原因指示以及延迟时间；
请求单元，设置为在所述用户设备的配置时间或延迟时间内不再尝试发起上行小数据传输请求。
在本发明实施例中，还提供了一种计算机存储介质，该计算机存储介质可以存储有执行指令，该执行指令用于执行上述实施例中的小数据传输的连接管理方法的实现。
本发明实施例的小数据传输的连接管理方法、SCEF实体、MME、UE，SCEF实体接收MME发送的始发数据传输请求后，或接收第三方服务设备如SCS/AS发送的数据传输配置请求后，向MME发送非IP数据连接状态信息，以使MME根据所述非IP数据连接状态信息，在MME本地设置SCEF连接的状态。本发明实施例的技术方案使得网络侧能够对SCEF连接的建立和使用加以管理，避免了终端发起上行小数据传输而无法正确地发送给SCS/AS，并可以进一步通知终端当前SCEF连接暂时不可用，使UE不必多次尝试发送上行小数据，从而避免网络信令的浪费。
附图说明
图1为增强的EPS系统的组成结构示意图；
图2为在基于图1所示的网络架构的UE附着到网络而实现非IP数据传输的流程示意图；
图3为本发明实施例的小数据传输的连接管理方法的流程图；
图4为本发明应用例一的小数据传输的连接建立方法的流程图；
图5为本发明应用例二的小数据传输的连接建立方法的流程图；
图6为本发明实施例的SCEF实体的组成结构示意图；
图7为本发明实施例的MME的组成结构示意图；
图8为本发明实施例的UE的组成结构示意图。
具体实施方式
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合 附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
图3为本发明实施例的小数据传输的连接管理方法的流程图，如图3所示，本发明实施例的小数据传输的连接管理方法包括以下处理步骤：
步骤301，SCEF实体接收移动性管理单元MME发送的始发数据传输请求后，或接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息。
本发明实施例中，第三方服务设备包括第三方服务平台(SCS，Service Capability Server)或第三方应用服务器(AS，Application Server)等网元设备。
步骤302，MME根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
本发明实施例中，所述SCEF实体接收所述MME发送的始发数据传输请求后，向所述MME发送非IP数据连接状态信息，具体包括：
所述SCEF接收所述MME发送的始发数据传输请求，所述始发数据传输请求中携带有UE发送的上行小数据包；
检查所述第三方服务设备的信息，在确定不存在对应的所述第三方服务设备的信息时，向所述MME发送始发数据传输响应消息，响应消息中携带有非IP数据连接状态信息。上述非IP数据连接状态信息包括：非IP数据传输配置未执行、或SCEF连接不可用。对应地，所述MME在本地设置SCEF连接的状态，包括：所述MME在本地设置SCEF连接状态为：SCEF连接不可用、或SCEF连接未激活。
本发明实施例中，所述SCEF接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息，包括：
所述SCEF接收所述第三方服务设备发送数据传输配置请求后，向归属用户服务器HSS发送数据传输授权请求，以使所述HSS向MME发送签约数据下载请求，所述签约数据中包含非IP数据连接状态。
具体地，SCS向SCEF发送数据传输配置请求；
SCEF向HSS发送数据传输授权请求；
HSS向MME发送签约数据下载请求，在签约数据中包含非IP数据连接状态；
MME根据HSS所发送的非IP数据连接状态，在本地设置SCEF连接状态。
本发明实施例中，作为一种实现方式，所述SCEF接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息，还可以包括：
所述SCEF接收所述第三方服务设备发送数据传输配置请求后，向归属用户服务器HSS发送数据传输授权请求；
接收所述HSS发送的数据传输授权响应后，向所述MME发送非IP数据连接状态。具体为：
SCS/AS向SCEF发送数据传输配置请求；
SCEF向HSS发送数据传输授权请求，从HSS收到数据传输授权响应；
SCEF向MME发送非IP数据连接状态；
MME根据SCEF所发送的非IP数据连接状态，在本地设置SCEF连接状态。
上述非IP数据连接状态信息包括：非IP数据传输配置已执行、或SCEF连接可用。对应地，所述MME在本地设置SCEF连接的状态，包括：
所述MME在本地设置SCEF连接的状态为：SCEF连接可用、或SCEF连接已激活。
本发明实施例中，所述非IP数据连接状态信息包括非IP数据传输配置未执行、或SCEF连接不可用时，本发明实施例还可以包括以下步骤：
在所述MME接收所述UE发送的NAS数据传输请求后，向UE发送拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因的指示。所述失败原因的指示包括：SCEF连接不可用、或SCEF连接未激活。
本发明实施例中，所述MME向UE发送拒绝NAS数据传输请求的消息时，还可发送延迟时间(Back-off time)的信息。
本发明实施例中，所述UE接收所述MME发送的失败原因指示后，根据所述UE配置的时间，或根据所述MME发送的延迟时间的信息，在配置时间或延迟时间内不再尝试发起上行小数据传输请求。
以下通过具体应用例，对本发明实施例的技术方案作进一步详细阐述。
应用例一
图4是本发明的SCEF向MME返回非IP数据连接状态，MME据此设置SCEF连接状态，并根据SCEF连接状态决定是否接收UE发起的上行小数据传输。
如图4所示，本应用例的小数据传输的连接管理方法包括以下处理步骤：
4A01～4A09，UE附着后，发起上行小数据传输，MME根据SCEF所返回的非IP数据连接状态，设置SCEF连接状态。具体地，
4A01，UE附着到网络，网络为其创建SCEF连接，其后，UE进入空闲态。如图2中2A01～2A07中所示；
4A02，UE从空闲态，向eNodeB发起RRC连接请求，携带NAS数据包，NAS数据包中携带UE要发送的上行小数据包；
4A03，eNodeB向MME发起上行NAS数据传输请求，其中携带在前述步骤的NAS数据包；
4A04，MME收到eNodeB发送的上行NAS数据传输请求，向SCEF发送始发数据传输消息，携带UE发送的小数据包；
4A05，SCEF根据SCS信息，判断是否拒绝MME的始发数据传输请 求；
在该步骤中，SCEF检查SCS信息，即检查该SCEF连接是否有对应的SCS信息，也即检查是否有SCS请求过非IP数据传输配置流程。
如无SCS请求过非IP数据传输配置流程，则拒绝MME发送的上行NAS数据传输请求。
4A06，SCEF向MME返回始发数据传输响应，其中携带非IP数据连接状态；
在本步骤中，非IP数据连接状态，可以是：非IP数据传输配置未执行、或SCEF连接不可用。该非IP数据连接状态，可以由一个失败原因来表示。
4A07，MME根据SCEF所返回的始发数据传输响应，设置SCEF连接状态；
在本例中，SCEF在始发数据传输响应携带的非IP数据连接状态，若指示为：非IP数据传输配置未执行、或SCEF连接不可用，则MME在本地设置对应的SCEF连接的状态为“SCEF不可用”、或“SCEF连接未激活”状态。
4A08，MME向eNodeB返回上行NAS数据传输响应，携带失败原因；
在本步骤中，MME返回的失败原因可以是：SCEF连接不可用、或SCEF连接未激活。当UE收到MME返回的失败原因后，可在一定的时间内(该时间由UE自行设置)，不尝试发起上行小数据传输流程。
进一步地，MME在返回失败原因的同时，还可以携带一个延迟时间(Back-off time)，该延迟时间指示UE在所述延迟时间内不应尝试发起上行小数据传输流程。
4A09，eNodeB向UE返回RRC连接响应，携带前述步骤中MME所携带的失败原因；
4B01～4B07，SCS/AS向SCEF发送数据传输配置请求，SCEF根据该 请求，触发MME设置SCEF连接状态。具体地，
4B01，SCS/AS向SCEF发送数据传输配置请求；
4B02，SCEF向HSS发送数据传输授权请求；
4B03，HSS对SCEF进行授权检查，返回数据传输授权响应；
4B04，SCEF收到数据传输授权响应后，向SCS/AS返回数据传输配置响应；
4B05，SCEF向MME发送通知请求消息，携带非IP数据连接状态；
在本步骤中，非IP数据连接状态，可以是：非IP数据传输配置已执行、或SCEF连接已可用。
4B06，MME根据SCEF发送的通知请求消息，在本地设置SCEF连接状态，设置为“SCEF连接已可用”、或“SCEF连接已激活”；
4B07，MME向SCEF发送通知响应消息。
需要说明的是，步骤4B05～4B07，可以发生在步骤4B04前。此后，如果UE从空闲态发起上行小数据传输，如步骤4C01～4C02，MME根据SCEF连接状态决定是否继续向上投递UE发送的小数据包。
应用例二：
图5为本发明的实施例的HSS向MME发送签约数据下载，MME根据HSS的消息，设置SCEF连接状态，并根据SCEF连接状态决定是否接收UE发起的上行小数据传输。
如图5所示，本应用例的小数据传输的连接管理方法包括以下处理步骤：
5A01～5A09，如图4中4A01～4A09所示，UE附着后，发起上行小数据传输，MME根据SCEF所返回的失败原因，设置SCEF连接状态。
5B01～5B07，HSS根据SCEF发送的数据传输授权请求，向MME下发签约数据，触发MME设置SCEF连接状态。具体地，
5B01，SCS/AS向SCEF发送数据传输配置请求；
5B02，SCEF向HSS发送数据传输授权请求；
5B03，HSS向MME发送签约数据下载请求消息，在UE签约数据中，携带非IP数据连接状态；
在本步骤中，仅当HSS对SCEF执行授权成功后，才向MME发送UE签约数据，携带非IP数据连接状态。非IP数据连接状态，可以是：非IP数据传输配置已执行、或SCEF连接已可用。
具体地，非IP数据连接状态，可以包含在APN配置信息中。
5B04，MME根据HSS下发的签约数据，在本地设置SCEF连接状态，设置为“SCEF连接已可用”、或“SCEF连接已激活”；
5B05，MME向HSS发送签约数据下载响应消息；
5B06，HSS对SCEF进行授权检查，返回数据传输授权响应；
5B07，SCEF收到数据传输授权响应后，向SCS/AS返回数据传输配置响应；
此后，如果UE从空闲态发起上行小数据传输，如步骤4C01～4C02，MME根据SCEF连接状态决定是否继续向上投递UE发送的小数据包。
图6为本发明实施例的SCEF实体的组成结构示意图，如图7所示，本发明实施例的SCEF实体包括第一接收单元60和第一发送单元61，其中：
第一接收单元60，设置为接收移动性管理单元MME发送的始发数据传输请求，或接收第三方服务设备发送的数据传输配置请求；
第一发送单元61，设置为向所述MME发送非IP数据连接状态信息，以使所述MME根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
图6所示的SCEF实体的基础上，本发明实施例的SCEF实体还可以包括：检查单元(图6中未示出)和第二发送单元(图6中未示出)；其 中，
所述第一接收单元60，还设置为接收所述MME发送的始发数据传输请求，所述始发数据传输请求中携带有UE发送的上行小数据包；
检查单元，设置为检查所述第三方服务设备的信息，在确定不存在对应的所述第三方服务设备的信息时，触发所述第二发送单元；
第二发送单元，设置为向所述MME发送始发数据传输响应消息，所述响应消息中携带有非IP数据连接状态信息。
本发明实施例中，所述非IP数据连接状态信息包括：
非IP数据传输配置未执行、或SCEF连接不可用。
本发明实施例中，在图6所示的SCEF实体的基础上，本发明实施例的SCEF实体还可以包括：第三发送单元(图6中未示出)；其中，
所述第一接收单元60，还设置为接收所述第三方服务设备发送数据传输配置请求，并触发所述第三发送单元；
第三发送单元，设置为向归属用户服务器HSS发送数据传输授权请求，以使所述HSS向MME发送签约数据下载请求，所述签约数据中包含非IP数据连接状态。
本发明实施例中，在图6所示的SCEF实体的基础上，本发明实施例的SCEF实体还可以包括：第四发送单元(图6中未示出)、第二接收单元(图6中未示出)和第五发送单元；其中，
所述第一接收单元，还设置为接收所述第三方服务设备发送数据传输配置请求，并触发所述第四发送单元；
第四发送单元，设置为向归属用户服务器HSS发送数据传输授权请求；
第二接收单元，设置为接收所述HSS发送的数据传输授权响应后，触发所述第五发送单元；
第五发送单元，设置为向所述MME发送非IP数据连接状态。
本发明实施例中，所述非IP数据连接状态信息包括：
非IP数据传输配置已执行、或SCEF连接可用。
本领域技术人员应当理解，图6所示的SCEF实体中的各单元的实现功能可参照前述小数据传输的连接管理方法的各实施例及应用例的相关描述而理解。接收单元及发送单元可以通过相应的网络接口实现，如有线接口。检查单元等可通过微处理器、大型可编程阵列FPGA或相应的芯片构成。
图7为本发明实施例的MME的组成结构示意图，如图7所示，本发明实施例的MME包括第一接收单元70和设置单元71，其中：
第一接收单元70，设置为接收服务能力开放功能SCEF实体发送的非IP数据连接状态信息；
设置单元71，设置为根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
本发明实施例中，所述第一接收单元70具体包括：第一接收子单元(图7中未示出)、第一发送子单元(图7中未示出)和第二接收子单元(图7中未示出)，其中：
第一接收子单元，设置为接收用户设备UE发送的包含在非接入层NAS中的上行小数据包，并触发所述第一发送子单元；
第一发送子单元，设置为向所述SCEF实体发送始发数据传输请求，所述始发数据传输请求中携带有所述上行小数据包；
第二接收子单元，设置为接收所述SCEF实体发送的始发数据传输响应消息，所述响应消息中携带有非IP数据连接状态信息。
在图7所示的MME的基础上，本发明实施例的MME还可以包括：
第二接收单元(图7中未示出)，设置为接收归属用户服务器HSS发送的签约数据下载请求，所述签约数据中包含非IP数据连接状态。
本发明实施例中，所述非IP数据连接状态信息包括：
非IP数据传输配置已执行、或SCEF连接可用；
对应地，所述设置单元71，还设置为在本地设置SCEF连接的状态为，SCEF连接可用、或SCEF连接已激活。
在图7所示的MME的基础上，本发明实施例的MME还可以包括：第四接收单元(图7中未示出)和发送单元(图7中未示出)；
所述设置单元71，还设置为在所述非IP数据连接状态信息包括非IP数据传输配置未执行、或SCEF连接不可用时，在本地设置SCEF连接的状态为SCEF连接不可用、或SCEF连接未激活；
对应地，第四接收单元，还设置为接收所述UE发送的NAS数据传输请求，并触发所述发送单元；
发送单元，设置为向UE发送拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因的指示。
本发明实施例中，所述失败原因的指示包括：SCEF连接不可用、或SCEF连接未激活。
本发明实施例中，所述发送单元在向UE发送拒绝NAS数据传输请求的消息时，还发送延迟时间的信息。
本领域技术人员应当理解，图7所示的MME中的各单元的实现功能可参照前述小数据传输的连接管理方法的各实施例及应用例的相关描述而理解。接收单元及发送单元可以通过相应的网络接口实现，如有线接口。设置单元等可通过微处理器、大型可编程阵列FPGA或相应的芯片构成。
图8为本发明实施例的UE的组成结构示意图，如图8所示，本发明实施例的UE包括发送单元80、接收单元81和请求单元82，其中：
发送单元80，设置为向移动性管理单元MME发送非接入层NAS数据传输请求，其中，在NAS中包含上行小数据包；
接收单元81，设置为接收所述MME发送的拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因指示、或者失败原因指示以及延迟时 间；
请求单元82，设置为在所述用户设备的配置时间或延迟时间内不再尝试发起上行小数据传输请求。
本领域技术人员应当理解，图8所示的UE中的各单元的实现功能可参照前述小数据传输的连接管理方法的各实施例及应用例的相关描述而理解。接收单元及发送单元可以通过相应的网络接口实现，如有线接口。
本发明实施例所记载的技术方案之间，在不冲突的情况下，可以任意组合。
在本发明所提供的几个实施例中，应该理解到，所揭露的方法和智能设备，可以通过其它的方式实现。以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元，即可以位于一个地方，也可以分布到多个网络单元上；可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案的目的。
另外，在本发明各实施例中的各功能单元可以全部集成在一个第二处理单元中，也可以是各单元分别单独作为一个单元，也可以两个或两个以上单元集成在一个单元中；上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。
工业实用性
本发明实施例的小数据传输的连接管理方法、SCEF实体、MME、UE，SCEF实体接收MME发送的始发数据传输请求后，或接收第三方服务设备如SCS/AS发送的数据传输配置请求后，向MME发送非IP数据连接状态信息，以使MME根据所述非IP数据连接状态信息，在MME本地设置SCEF连接的状态。本发明实施例的技术方案使得网络侧能够对SCEF连接的建立和使用加以管理，避免了终端发起上行小数据传输而无法正确地发送给SCS/AS，并可以进一步通知终端当前SCEF连接暂时不可用，使UE不必多次尝试发送上行小数据，从而避免网络信令的浪费。

Claims (26)

  1. 一种小数据传输的连接管理方法，所述方法包括：
    服务能力开放功能SCEF实体接收移动性管理单元MME发送的始发数据传输请求后，或接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息；
    所述MME根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
  2. 根据权利要求1所述的小数据传输的连接管理方法，其中，所述SCEF实体接收所述MME发送的始发数据传输请求后，向所述MME发送非IP数据连接状态信息，包括：
    所述SCEF接收所述MME发送的始发数据传输请求，所述始发数据传输请求中携带有UE发送的上行小数据包；
    检查所述第三方服务设备的信息，在确定不存在对应的所述第三方服务设备的信息时，向所述MME发送始发数据传输响应消息，所述响应消息中携带有非IP数据连接状态信息。
  3. 根据权利要求2所述的小数据传输的连接管理方法，其中，所述非IP数据连接状态信息包括：
    非IP数据传输配置未执行、或SCEF连接不可用。
  4. 根据权利要求2所述的小数据传输的连接管理方法，其中，所述MME在本地设置SCEF连接的状态，包括：
    所述MME在本地设置SCEF连接状态为：SCEF连接不可用、或SCEF连接未激活。
  5. 根据权利要求1所述的小数据传输的连接管理方法，其中，所述SCEF接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息，包括：
    所述SCEF接收所述第三方服务设备发送数据传输配置请求后，向归属用户服务器HSS发送数据传输授权请求；
    所述HSS向MME发送签约数据下载请求，所述签约数据中包含非IP数据连接状态。
  6. 根据权利要求1所述的小数据传输的连接管理方法，其中，所述SCEF接收第三方服务设备发送的数据传输配置请求后，向所述MME发送非IP数据连接状态信息，包括：
    所述SCEF接收所述第三方服务设备发送数据传输配置请求后，向归属用户服务器HSS发送数据传输授权请求；
    接收所述HSS发送的数据传输授权响应后，向所述MME发送非IP数据连接状态。
  7. 根据权利要求5或6所述的小数据传输的连接管理方法，其中，所述非IP数据连接状态信息包括：
    非IP数据传输配置已执行、或SCEF连接可用。
  8. 根据权利要求5或6所述的小数据传输的连接管理方法，其中，所述MME在本地设置SCEF连接的状态，包括：
    所述MME在本地设置SCEF连接的状态为：SCEF连接可用、或SCEF连接已激活。
  9. 根据权利要求1所述的小数据传输的连接管理方法，其中，所述非IP数据连接状态信息包括非IP数据传输配置未执行、或SCEF连接不可用时，所述MME在本地设置SCEF连接的状态，包括：
    所述MME在本地设置SCEF连接的状态为：SCEF连接不可用、或SCEF连接未激活。
  10. 根据权利要求9所述的小数据传输的连接管理方法，其中，所述方法还包括：
    在所述MME接收所述UE发送的NAS数据传输请求后，向UE发送拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因的指示；所述失败原因的指示包括：SCEF连接不可用、或SCEF连接未激活。
  11. 根据权利要求10所述的小数据传输的连接管理方法，其中，所述MME向UE发送拒绝NAS数据传输请求的消息时，还发送延迟时间的信息。
  12. 根据权利要求11所述的小数据传输的连接管理方法，其中，所述方法还包括：
    所述UE接收所述MME发送的失败原因指示后，根据所述UE配置的时间，或根据所述MME发送的延迟时间的信息，在配置时间或延迟时间内不再尝试发起上行小数据传输请求。
  13. 一种服务能力开放功能SCEF实体，所述SCEF实体包括：第一接收单元和第一发送单元，其中：
    第一接收单元，设置为接收移动性管理单元MME发送的始发数据传输请求，或接收第三方服务设备发送的数据传输配置请求；
    第一发送单元，设置为向所述MME发送非IP数据连接状态信息，以使所述MME根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
  14. 根据权利要求13所述的SCEF实体，其中，所述SCEF实体还包括：检查单元和第二发送单元；其中，
    所述第一接收单元，还设置为接收所述MME发送的始发数据传输请求，所述始发数据传输请求中携带有UE发送的上行小数据包；
    检查单元，设置为检查所述第三方服务设备的信息，在确定不存在对应的所述第三方服务设备的信息时，触发所述第二发送单元；
    第二发送单元，设置为向所述MME发送始发数据传输响应消息，所述响应消息中携带有非IP数据连接状态信息。
  15. 根据权利要求14所述的SCEF实体，其中，所述非IP数据连接状态信息包括：
    非IP数据传输配置未执行、或SCEF连接不可用。
  16. 根据权利要求14所述的SCEF实体，其中，所述SCEF实体还包括：第三发送单元；其中，
    所述第一接收单元，还设置为接收所述第三方服务设备发送数据传输配置请求，并触发所述第三发送单元；
    第三发送单元，设置为向归属用户服务器HSS发送数据传输授权请求，以使所述HSS向MME发送签约数据下载请求，所述签约数据中包含非IP数据连接状态。
  17. 根据权利要求13所述的SCEF实体，其中，所述SCEF实体还包括：第四发送单元、第二接收单元、第二接收单元和第五发送单元；其中，
    所述第一接收单元，还设置为接收所述第三方服务设备发送数据传输配置请求，并触发所述第四发送单元；
    第四发送单元，设置为向归属用户服务器HSS发送数据传输授权请求；
    第二接收单元，设置为接收所述HSS发送的数据传输授权响应后，触发所述第五发送单元；
    第五发送单元，设置为向所述MME发送非IP数据连接状态。
  18. 根据权利要求16或17所述的SCEF实体，其中，所述非IP数据连接状态信息包括：
    非IP数据传输配置已执行、或SCEF连接可用。
  19. 一种移动性管理单元，所述移动性管理单元包括：第一接收单元和设置单元，其中：
    第一接收单元，设置为接收服务能力开放功能SCEF实体发送的非IP数据连接状态信息；
    设置单元，设置为根据所述非IP数据连接状态信息，在本地设置SCEF连接的状态。
  20. 根据权利要求19所述的移动性管理单元，其中，所述第一接收 单元包括：第一接收子单元、第一发送子单元和第二接收子单元，其中：
    第一接收子单元，设置为接收用户设备UE发送的包含在非接入层NAS中的上行小数据包，并触发所述第一发送子单元；
    第一发送子单元，设置为向所述SCEF实体发送始发数据传输请求，所述始发数据传输请求中携带有所述上行小数据包；
    第二接收子单元，设置为接收所述SCEF实体发送的始发数据传输响应消息，所述消息中携带有非IP数据连接状态信息。
  21. 根据权利要求19所述的移动性管理单元，其中，所述移动性管理单元还包括：
    第二接收单元，设置为接收归属用户服务器HSS发送的签约数据下载请求，所述签约数据中包含非IP数据连接状态。
  22. 根据权利要求21所述的移动性管理单元，其中，所述非IP数据连接状态信息包括：
    非IP数据传输配置已执行、或SCEF连接可用；
    对应地，所述设置单元，还设置为在本地设置SCEF连接的状态为，SCEF连接可用、或SCEF连接已激活。
  23. 根据权利要求19所述的移动性管理单元，其中，所述移动性管理单元还包括：第四接收单元和发送单元；
    所述设置单元，还设置为在所述非IP数据连接状态信息包括非IP数据传输配置未执行、或SCEF连接不可用时，在本地设置SCEF连接的状态为SCEF连接不可用、或SCEF连接未激活；
    对应地，第四接收单元，还设置为接收所述UE发送的NAS数据传输请求，并触发所述发送单元；
    发送单元，设置为向UE发送拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因的指示。
  24. 根据权利要求23所述的移动性管理单元，其中，所述失败原因 的指示包括：SCEF连接不可用、或SCEF连接未激活。
  25. 根据权利要求23所述的移动性管理单元，其中，所述发送单元在向UE发送拒绝NAS数据传输请求的消息时，还发送延迟时间的信息。
  26. 一种用户设备，所述用户设备包括：发送单元、接收单元和请求单元，其中：
    发送单元，设置为向移动性管理单元MME发送非接入层NAS数据传输请求，其中，在NAS中包含上行小数据包；
    接收单元，设置为接收所述MME发送的拒绝NAS数据传输请求的消息，拒绝消息中携带有失败原因指示、或者失败原因指示以及延迟时间；
    请求单元，设置为在所述用户设备的配置时间或延迟时间内不再尝试发起上行小数据传输请求。
PCT/CN2017/085534 2016-05-26 2017-05-23 一种小数据传输的连接管理方法、scef实体、mme及ue WO2017202305A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610361435.8 2016-05-26
CN201610361435.8A CN107438291B (zh) 2016-05-26 2016-05-26 一种小数据传输的连接管理方法、scef实体、mme及ue

Publications (1)

Publication Number Publication Date
WO2017202305A1 true WO2017202305A1 (zh) 2017-11-30

Family

ID=60412128

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/085534 WO2017202305A1 (zh) 2016-05-26 2017-05-23 一种小数据传输的连接管理方法、scef实体、mme及ue

Country Status (2)

Country Link
CN (1) CN107438291B (zh)
WO (1) WO2017202305A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11382025B2 (en) 2019-02-26 2022-07-05 At&T Intellectual Property I, L.P. Object-resource model to facilitate IoT services

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108337300B (zh) * 2018-01-19 2021-03-12 苏州大学 一种应用于窄带物联网的人机接口通信方法和系统
CN110139264B (zh) * 2018-02-09 2021-10-15 华为技术有限公司 NB-IoT网络的通信方法、装置及存储介质
WO2020118562A1 (en) 2018-12-12 2020-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for ip and non-ip data communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150264512A1 (en) * 2014-03-14 2015-09-17 Puneet K. Jain Conveyance of application communication patterns from an external application server to a 3rd generation partnership project system
CN105392112A (zh) * 2015-11-30 2016-03-09 中国联合网络通信集团有限公司 Mtc设备信息的保护方法、设备及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7873710B2 (en) * 2007-02-06 2011-01-18 5O9, Inc. Contextual data communication platform
CN101272621B (zh) * 2007-03-19 2014-05-21 华为技术有限公司 用户设备能力信息传输方法
EP3127366B1 (en) * 2014-03-31 2021-03-24 Convida Wireless, LLC Overload control and coordination between m2m service layer and 3gpp networks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150264512A1 (en) * 2014-03-14 2015-09-17 Puneet K. Jain Conveyance of application communication patterns from an external application server to a 3rd generation partnership project system
CN105392112A (zh) * 2015-11-30 2016-03-09 中国联合网络通信集团有限公司 Mtc设备信息的保护方法、设备及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
JAIN, P.: "Digital Cellular Telecommunications System (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Architecture enhancements to Facilitate Communications with Packet Data Networks and Applications (3GPP TS 23.682 version 13.5.0 Release 13", ETSI TS 123 682, 14 April 2016 (2016-04-14), pages 43 - 51 and 76-82 *
SCHMITT, P.: "LTE; Universal Mobile Telecommunications System (UMTS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) Interfaces for Interworking with Packet Data Networks and Applications (3GPP TS 29.128 version 13.0.0 Release 13", ETSI TS 129 128, 20 May 2016 (2016-05-20), pages 1 - 25, XP051046300 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11382025B2 (en) 2019-02-26 2022-07-05 At&T Intellectual Property I, L.P. Object-resource model to facilitate IoT services

Also Published As

Publication number Publication date
CN107438291B (zh) 2020-08-11
CN107438291A (zh) 2017-12-05

Similar Documents

Publication Publication Date Title
US11617072B2 (en) Reliable data delivery over non-access stratum
US10708133B2 (en) Method for transmitting and receiving signal related to monitoring by SCEF in wireless communication system and apparatus for the same
US10219143B2 (en) Data transmission method, mobility management entity, and mobile terminal
JP2020506620A (ja) 要求に対する応答方法及びネットワーク装置
BR112020002580A2 (pt) dipositivo sem fio e entidade ou função de rede núcleo para prover controle de gap de serviço e métodos de operação relacionados
WO2017202194A1 (zh) 一种连接建立方法、scef实体、mme、计算机存储介质
US20110182244A1 (en) Method for supporting context management by home node-b
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
WO2017202305A1 (zh) 一种小数据传输的连接管理方法、scef实体、mme及ue
WO2018137152A1 (zh) 短消息传输方法、设备和系统
US10244567B2 (en) ICN connectivity awareness
JP6191768B2 (ja) 移動無線通信装置からのデータ転送
WO2011050663A1 (zh) 支持本地ip访问的通信系统中隧道更新方法与系统
WO2011085623A1 (zh) 本地接入网关获取终端的寻呼信息的方法和系统
WO2011032522A1 (zh) 一种实现本地接入的系统及方法
WO2011035719A1 (zh) 一种释放本地连接的方法及系统
WO2015010325A1 (zh) 数据传输方法及装置
WO2011063692A1 (zh) 一种数据缓存单元区分网络链接类型的方法及系统
US11974355B2 (en) Indication information sending method, apparatus and system, and storage medium
WO2012129997A1 (zh) 本地访问连接的处理方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17802151

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17802151

Country of ref document: EP

Kind code of ref document: A1