Enabling small data usage in 3GPP networks

By enabling direct communication between core network nodes to manage small data decisions, the inefficiencies in 3GPP networks for MTC applications are addressed, optimizing data transfer and reducing overhead through network-aware data procedures.

JP7588667B2Active Publication Date: 2024-11-22INTERDIGITAL PATENT HOLDINGS INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023014016
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2015-04-22
Filing Date
2023-02-01
Publication Date
2024-11-22
Estimated Expiration
2036-04-22

AI Technical Summary

Technical Problem

Existing 3GPP networks are inefficient in handling small data transmissions by Machine Type Communications (MTC) applications due to significant signaling overhead and resource wastage, particularly when UEs transition between idle and connected states.

Method used

The proposed solution involves direct communication between core network nodes to manage small data decisions, optimizing data transfer through the control plane or data plane by configuring UEs to use efficient data procedures based on network conditions, using enhanced interfaces and message formats to provision small data flow information.

Benefits of technology

This approach reduces signaling overhead and resource wastage, enhancing the efficiency of small data transmission in 3GPP networks by making data delivery decisions based on real-time network requirements, thereby improving resource management and reducing delays.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007588667000029
    Figure 0007588667000029
  • Figure 0007588667000030
    Figure 0007588667000030
  • Figure 0007588667000031
    Figure 0007588667000031
Patent Text Reader

Abstract

A method and apparatus are provided for identifying services or flows that should be characterized as small data in a user equipment (UE) or core network and determining when to employ optimized small data procedures. In one embodiment, a mobile management entity (MME) receives a first message from a UE. The first message includes an attach request that includes an indication that the UE supports a small data procedure and, alternatively or in addition, an attach request that the UE use the small data procedure. The MME also receives a second message from a network node, such as a home subscriber server (HSS). The second message indicates one or more packet data network (PDN) connections for which the small data procedure should be used and indicates a type of small data procedure corresponding to each of the one or more PDN connections.
Need to check novelty before this filing date? Find Prior Art

Description

[Background technology]

[0001] (Citation of Related Application) This application is the benefit of U.S. Provisional Patent Application No. 62 / 151,088 (filed April 22, 2015). The benefit of this application is claimed, and the disclosures of the above applications are incorporated herein by reference as if set forth in their entirety. is cited in the book.

[0002] (background) Machine Type Communication (MTC) applications often transmit small amounts of data. The small amount of data that is transmitted or received may generally be referred to as small data. When a "small data" application engages in infrequent communication sessions, In this regard, resources within a communication network, for example a 3GPP system, are used inefficiently.

[0003] The MTC application on a given User Equipment (UE) provides services to the 3GPP network. If you need to get data from a network, you must first "attach" to the network. The attach procedure may be performed by the UE after it is powered on. 1 illustrates an example attachment procedure performed within a 3GPP network 200. At the level, the attach procedure informs the network about the presence of the UE; The attach procedure establishes the default bearer in the network and ensures that traffic With reference to FIG. 1A, an example is shown in which According to the method, in 201, the UE 202 receives an identification of the UE 202, a type of connection requested (e.g. For example, a packet data network (PDN) type), and optionally, the UE 202 Access Point, a string that refers to the packet data network to which you are requesting access In response to this request, the ISP issues an attach request, which includes various parameters such as the ISP's access point name (APN). The information is transferred from the 3GPP base station 204 to a mobility management entity (MME) 206. The MME 206 uses the APN information to determine which packet data network to connect to. Select a network and then use PDN Type to specify the type of connection (for example, IPv4 and The MME 206 determines the home subscriber server (HSS) 20 By querying the subscription profile of the device contained within 8 ( 205a), the UE 202 may verify that it has access to the PDN. If the MME 202 does not provide an APN, for example, the MME 206 may The MME and HSS may use the default APN defined as part of the APN profile. The exchanges between (at 205a and 205b) include location update requests / replies or subscriber In either case, the MME 206 receives the PDS and As shown, in 207, the MM E may then set up a bearer in the 3GPP network 200. At 209, the MM The E 206 may issue an attach accept message to the UE 202 via the base station 204. At 211, the UE 202 may then transmit to the MME 206 via the base station 204. The attach procedure may be completed with an attach complete message.

[0004] After attachment, e.g., the attachment procedure shown in FIG. 1A, occurs, a given user When an application on the User Equipment (UE) is not communicating, the radio bearer is released. As used herein, the term "IDLE" refers to a state in which the UE is in an idle state. Unless otherwise specified, a UE in idle state or mode shall not use the Evolved Packet Core (EP C) UEs in EMM-REGISTERED state and in progress This refers to a UE that is in the Enhanced Packet System (EPS) Connection Management (ECM) Idle state. As a further embodiment, a given application may establish a connection with a UE in an idle state. If the UE wishes to establish a connection, it establishes a data bearer and signals a connection to the network. By doing so, it will be necessary to transition to CONNRCTED mode. As used in this document, unless otherwise specified, a UE in connected mode shall not be This refers to a UE that is in the

[0005] For UEs that transmit or receive only small amounts of data, the above transitions can be used for example in moderation. The relative signaling overhead for performing packet data transfers is large, leading to inefficiencies. This resource issue is not limited to MTC applications, but also applies to small data This can be applied to any application that communicates. To support the transmission of small data with network impact, the solution is , 3GPP TR 23.887 “Machine-Type and other M obile Data Applications Communications E (Network effects are, for example, This refers to the delays associated with signal transmission overhead, network resource usage, and reallocation. 3GPP for Small Data and Device Trigger Extensions (SDDTE) The solutions described in TR 23.887 fall into two broad categories: 1) Radio Access Network for Small Data (SD) (RAN) control plane usage, 2) data plane usage for SD.

[0006] In an exemplary method of using the RAN control plane for small data, the data is Signaling between evolved Node B (eNB) and User Equipment (UE) over the wire interface It is transferred via a transport radio bearer (SRB). From the eNB to the core network (CN) The transfer is via the S1-MME interface to the mobility management entity (MME). CN control plane via S1-U or S1-U to the Serving Gateway (S-GW) The CN data plane over the LTE bearer interface may be used. In this example, small data is transported to the eNB on a radio bearer. It will be possible.

[0007] In an exemplary method of using a data plane for small data, the data is The data is transferred between the eNB and the UE via the Data Radio Bearer (DRB) on the interface. The transfer from eNB to CN is often performed via the S1-U interface to the S-GW. However, in some cases, e.g. Additional conditions apply, such as the use of stateless gateways or the restriction to a single bearer. With reference to FIG. 1B, this example as implemented in the LTE bearer architecture may be In this case, small data is sent to the S-GW over E-RAB or to the P-GW over EPS bearer. will be transported to

[0008] Generally, in this specification, idle mode (EMM-REGISTERED For a given UE in ECM-IDLE and ECM-IDLE states, the UE When the UE needs to perform a transfer procedure (e.g. TAU or detach) or If it has uplink data to transmit, it will select the connection mode (ECM-C The UE recognizes that it needs to transition to the ONNECTED state. When the UE wishes to move to the ECM connected state in order to The service request procedure synchronizes the UE and CN in bearer information and The established data bearer is then transmitted by the UE to the It can be used to transmit data.

[0009] The case where the UE transitions from ECM idle to ECM connected and transmits data is SDDT In the above solution, as described in 3GPP TR23.887 for E The exemplary solution described in 3GPP TR 23.887 is New procedures (e.g. data transfer without service request procedures) may be used. require that procedures be used or modifications to existing procedures (e.g., service Requests for modifications to the requested procedure. Often, new / modified procedures The call is initiated from the UE.

[0010] Referring to FIG. 2, the Policy and Charging Control (PCC) architecture is shown. The CC architecture is based on TS 23.203 "Policy and charging It is defined by 3GPP in the "Network Control Architecture" The PCC architecture stores policies, policy rules, QoS rules, and charging information. The interface shown in Figure 2 is used to implement the This is explained in detail in Section 5.2, but for convenience it is summarized below. The interface used is the Internet Protocol (IP) P) Used to provision flows and their corresponding rules.

[0011] Referring to Figure 2, the AF (third-party application server) uses the Rx interface Use it to collect application-level session information (e.g. IP filter information, bandwidth The PFC forwards the requested information (bandwidth requirements, sponsor data, etc.) to the Policy and Charging Rules Function (PCRF). CRF forms Policy and Charging Control (PCC) rules based on IP flow information. ,This PC is connected to the Policy and Charging Enforcement Function (PCEF) using the Gx interface. Based on the IP flow information, the PCRF provisions QoS rules. It forms a group and uses the Gxx interface to provide bearer binding and event reporting functions ( Provision this QoS rule on the Sp / Ud interface. The PCRF obtains subscription information about the IP flow based on the subscriber ID. The PCRF uses the Sp interface to It interacts with the Repository Profile Repository (SPR) and the User Data Repository ( Use the Ud interface for UDRs.

[0012] Still referring to FIG. 2, the interface used to transfer billing related information is The PCRF uses the Sd interface to make ADC decisions. The PCRF signals the configuration to the Traffic Detection Function (TDF). The policy counter status information is sent to the OCS using the Gz interface. The service enables the transport of service data flow-based offline charging information. The Gyn interface is used for ADC rule-based charging in TDF. The Gzn interface enables online credit control for For ADC rule-based charging, enable the transport of offline charging information. do.

[0013] Figure 3 shows the 3GPP architecture for machine type communication (MTC). Type communication generally occurs across different devices and / or applications without human interaction. The MTC device communicates with the service capabilities server (SCS). The 3GPP system can communicate with external MTC applications using the basic In addition, it provides a transport for machine-to-machine (M2M) device communication. Therefore, the 3GPP system may provide other value-added services for machine-type communications. In this document, different architecture models are also discussed. Based on the relationship between the 3GPP network operators and the 3GPP It is recognized that exemplary architecture extensions for MTC are described in 3GPP TS 23. 683 “Architecture enhancements to facilit ate communications with packet data network It is defined in TS23.683. The main architecture of the system is shown in Figure 3. MTC-IWF (Machine Type Communication - Interworking function) is introduced in the 3GPP system to Enables communication with one or more Service Capability Servers (SCS). It can be a standalone entity or a logical entity in another network element. The IWF hides the internal CN topology and transmits via a Diameter-based Tsp reference point. It relays or converts the information received and invokes specific functionality within the CN. Models are also defined in 3GPP TS 23.708. For example, the service capability The Special Scope Function (SCEF) is introduced in the 3GPP system to The SCEF enables communication between the Service Capability Server (SCE) and one or more Service Capability Servers (SCS). The SCEF may be a logical entity in a network entity or in another network element. It hides the internal CN topology, relays or transforms information received via API calls, and It interfaces with the core network nodes of For example, the SCEF calls the MTC-IWF, the HSS, the PCRF, the UDR, It can interface with MME, etc.

[0014] In this specification, 3GPP explores new small data delivery techniques for MTC communications. For example, the solution in TR23.887 is Carry small data transfers more efficiently by reducing transmission overhead However, existing approaches lack capacity and efficiency. . Summary of the Invention [Means for solving the problem]

[0015] As mentioned above, 3GPP is exploring new small data delivery techniques for MTC communications. The proposed technique is to transmit information to the non-access layer (NAS) via the control plane. This involves transmitting the data within a QoS (User Response) or Radio Resource Control (RRC) message. The document states that existing approaches make "small data" decisions based on downlink data. to the Service Capability Server (SCS) for uplink data, and to the User Equipment (UE) for uplink data. It is recognized that the present disclosure is directed to a user equipment (UE) or or the core network is providing services (or flows) that should be characterized as small data. The embodiments disclosed herein also address a method for identifying an optimized sequence. It also addresses when mall data procedures should be employed. The states may also be referred to synonymously or collectively as SCS / AS / AF. Application Server (AS) or Application Function (AF), e.g., MTC - IWF, Home Subscriber Server (HSS), Policy and Charging Rules Function (PCRF), User Data Repository (UDR), and Mobile Management Entity (MME) A method for directly communicating with a core network node is disclosed. Instead of communicating, the SCS / AS / AF communicates with the Service Capability Exposure Function (SCE It should be understood that the UE may communicate with a core network node via F).

[0016] In an exemplary embodiment, a core network (CN) controls small data (SD) communications. For example, which may be collectively referred to as AF / SCS / AS or any variation thereof, Application Function (AF) or Service Capability Server (SCS) or Application The Application Service (AS) is a service that provides a 3GPP network with a related to data flows so that decisions can be made regarding which flows should be considered “non-transitive data” In one aspect, the AF / SCS may provision the PCRF with the associated information. Provision small data flow information via the Rx interface. On the other hand, the AF / SCS provides the PCRF with a Tsp interface and an MTC-IW Provision small data flow information via F. In yet another aspect, AF / SCS has registered Ud / Mh in the subscription database (HSS / UDR). The small data flow information is provisioned via the interface. As explained in, the small data flow information provided to the 3GPP network is It can be used by 3GPP networks. For example, the core network can be used to The downlink data may be routed to the UE via a data distribution method. The small data flow information is transmitted to the 3GPP network as uplink data. Use small data delivery method to route towards 3GPP network It is used to configure the UE as follows: Small Data Flows in 3GPP Networks New subscription information that supports this is described herein. In the examples, additional information elements are described and existing information elements are modified. The information element is included in a message shared between the 3GPP network and the UE, It may support configuring the UE to use small data delivery in the front link.

[0017] In another exemplary embodiment, a device, for example a device including an MME, receives a first message The first message may be received from the UE indicating that the UE supports the small data procedure. Alternatively or in addition, the first This message contains an attack request that the UE use the small data procedure. The apparatus may also transmit the second message to a network node, e.g., a HS The second message should use the small data procedure. The second message may also indicate one or more PDN connections. The type of small data procedure corresponding to each can be indicated. Based on the received message, the device may respond to the first message. For example, the response may include a response indicating that the UE has received the second message. Small data using one of the small data procedures shown on this page The device may then include an Attach Response message including an indication that the device should function in the Attach Response mode. and use one of the small data procedures shown in the second message. The device may also transmit the small data shown in the second message. The data may be received from the UE according to one of the following procedures: The call data procedure may be indicated via Non-Access Stratum (NAS) messaging. .

[0018] This Summary is provided in a simplified form to illustrate some aspects of the invention that are further described below in the Detailed Description. This Summary is provided to introduce a selection of concepts. It is intended to identify key features or aspects of the claimed subject matter. It is not intended to identify essential features, but is used to limit the scope of the claimed subject matter. Moreover, it is not intended that the claimed subject matter be The present invention is not limited to limitations that address any or all of the disadvantages of the present invention.

[0019] To facilitate a more thorough understanding of the present application, like elements will be referred to with like numerals herein. Reference is made to the accompanying drawings, which are not to be construed as limiting the present application, It is intended to be illustrative only. [Brief description of the drawings]

[0020] [Figure 1A] FIG. 1A is a call flow illustrating an example attach procedure that may be performed in a 3GPP network. [Figure 1B] FIG. 1B is an exemplary diagram of an LTE architecture in which, among other things, the procedures shown in FIG. 1A may be performed. [Diagram 2] FIG. 2 is a block diagram depicting the Policy and Charging Control (PCC) logical architecture. [Diagram 3] FIG. 3 is a block diagram depicting the 3GPP architecture for machine type communications (MTC). [Figure 4] FIG. 4 is a call flow illustrating an exemplary embodiment of an Application Function (AF) session establishment. [Diagram 5] FIG. 5 depicts an additional interface, which may be referred to as a T7 interface, within the 3GPP MTC architecture shown in FIG. 3, according to an example embodiment. [Figure 6] FIG. 6 is a call flow illustrating service capability server (SCS) information provisioning via the Tsp and T7 interfaces depicted in FIG. [Figure 7] FIG. 7 is an example block diagram of a 3GPP interworking architecture. [Figure 8] FIG. 8 is a call flow over a Gx reference point illustrating an example pull delivery method (Policy and Charging Enforcement Function (PCEF) requested provisioning). [Figure 9] FIG. 9 is a call flow over a Gx reference point illustrating an exemplary push delivery method (unsolicited provisioning) according to an embodiment. [Figure 10] FIG. 10 is a call flow over a Gxx reference point illustrating an exemplary pull delivery method (QoS provisioning solicited by Bearer Binding and Event Reporting Function (BBERF)). [Figure 11] FIG. 11 is a call flow over a Gxx reference point illustrating an exemplary push delivery method (unsolicited QoS provisioning) according to an exemplary embodiment. [Figure 12] FIG. 12 depicts the current linkage of Traffic Flow Templates (TFT) with the bearer concept in the Evolved Packet System (EPS). [Figure 13] FIG. 13 depicts a small data (SD) TFT linked to a packet data network (PDN) connection, according to an example embodiment. [Figure 14] FIG. 14 depicts an exemplary graphical user interface (GUI) according to an exemplary embodiment. [Figure 15A] FIG. 15A is a system diagram of an example machine-to-machine (M2M) or Internet of Things (IoT) communication system in which one or more disclosed embodiments may be implemented. [Figure 15B] FIG. 15B is a system diagram of an example architecture that may be used within the M2M / IoT communication system illustrated in FIG. 15A. [Figure 15C] FIG. 15C is a system diagram of an example M2M / IoT terminal or gateway device that may be used within the communication system illustrated in FIG. 15A. [Figure 15D] FIG. 15D is a block diagram of an example computing system in which aspects of the communication system of FIG. 15A may be embodied. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] As used herein, unless otherwise specified, "IDLE" mode A User Equipment (UE) in the Evolved Packet Core (EPC) mobility management EMM-REGISTERED state and Evolved Packet EPS Connection Management (ECM) Idle State (ECM-IDLE stat e) A UE in "connected" mode refers to a UE in ECM connected state. As used herein, the term "small data filter" may refer to: 1) 3GPP TS 24.008 “Mobile radio interface La yer 3 specification;Core network protocol Packets as described in the Traffic Flow Template (TFT) in Filters, 2) RFC 3588 "Diameter Base Protocol" an IPFilterRule as described above, or 3) matching IP traffic The terms "small data information", " "Data flow information," and variations thereof, are used interchangeably herein and generally refer to Describe one or more characteristics associated with IP traffic that is considered mall data. For example, the small data information may include a small data filter. As used herein, unless otherwise specified, the term "small data plane" means It refers to a path through which small data can be transferred. In one embodiment, the path is a wireless access network. Network (RAN) control plane, RAN data plane, Core Network (CN) control plane It may be a combination of the CN control plane, and the CN data plane. In some cases, The combination will depend on the solution selected by 3GPP for small data transfer. As used herein, unless otherwise specified, the term "small data processor" refers to a "Losilla" is the approach chosen by 3GPP for the transfer of small data (e.g., messages and procedures). As mentioned above, several approaches One of these approaches is described in 3GPP TR 23.887. More than one thing can be accomplished.

[0022] As mentioned above, the proposed approach to managing small data is different from existing approaches. These techniques generally involve the transmission of data via a control plane or a data plane. In this specification, the approach discussed in 3GPP has been Data Decision" to the SCS for downlink data and to the SCS for uplink data. In other words, the user plane (e.g., IP-based Use existing procedures to transmit data via the SGi reference point of the or use existing procedures to use alternative small data delivery methods. It is up to the UE or SCS to decide whether to do so.

[0023] In this specification, it is considered that leaving the "small data decision" to the SCS or UE is inefficient. It will be appreciated that in some cases, the UE or SCS may be The SCS will make decisions based on what is best for the UE or SCS, not the network. For example, the UE may choose to always At the very least, the 3GPP core network may choose to use the fastest delivery method. For example, recognizing the network conditions, the present specification The network is better positioned to make decisions about the most efficient way to deliver data. It is recognized that a

[0024] According to various embodiments, the 3GPP core network controls the "small data decision". For example, in one aspect, for convenience, Service capability services that may be collectively referred to as SCS / AS (or variations thereof) The SCS or AS connects to the 3GPP network. It can provide the characteristics of the data flow between the CS / AS and its UE. As explained below, based on the information provided by the SCS / AS, the 3GPP network The network can instruct the UE when to use the small data plane; The 3GPP network transports downlink traffic from the SCS / AS as small data rates. The system can decide when to direct the aircraft to the tap plane.

[0025] In some cases, in the uplink, the UE may use a small data processor for data transmission. or use of existing service request procedures In this specification, the UE is required to make a decision based on the small data procedure. It is recognized that one should know when to start. In an exemplary embodiment, CN and and / or the SCS may allow the UE to request service via the Smart The UE can be configured to know when to use the call data procedure. In some cases, in the downlink, the network determines which flows / bearers are in the In an exemplary embodiment, the network determines whether the S Such a decision may be made based on flow information received from the CS.

[0026] Various inputs from the AS / SCS are now described. It is recognized that the service layer is best informed about the data rate needs of a given service. For example, the service layer is often thought of as a small amount of data, with services always being or whether a given service will track its activity through small data ( For example, it is expected that messages will be classified only periodically (e.g., as heartbeat messages). As a further example, in some cases the service layer may Know the number of packets that will be transmitted during the period and the size of the packets that are typically transmitted. In this specification, various information such as those mentioned above, e.g. If information in the service layer can be shared with the network, the network can use the information to It will be appreciated that the resources of the network can be managed in an efficient manner. For example, the network can create rules in real time based on the actual requirements of the service. This can be done.

[0027] In an exemplary embodiment, the Rx interface receives data flow information, e.g., The AF / SCS is extended to support data flow information. For example, the AF / SCS Through the interface, the flow information can be adjusted. Small data information associated with 2M applications is sent via the Rx interface. In another exemplary aspect described below, A new attribute-value pair (AVP) is added to the Rx interface to convey small data information to the existing AA. The AAR is added for inclusion in the Diameter message. With reference to the AF shown, as used herein, the AF refers to an MTC server, an M2M It may be a server, an SCS, etc., and therefore the AF is also generally referred to as a network node. It should be understood that this may be the case.

[0028] Referring to Table 1 below, according to an exemplary embodiment, the AF / SCS may Provides small data flow information associated with each application via the The information is pre-provisioned in the AF / SCS by the operator. Alternatively or additionally, the application may By monitoring traffic and collecting statistical data associated with applications, Therefore, the information can be obtained. Table 1 shows the information provided to the PCRF for each application. The following table includes exemplary information elements that may be included in the . , may be conditional (e.g., traffic mode). As described, the PCRF This information is used to set small data rules (e.g. PCC rules, QoS rules, etc.) ) can be adopted. It should be understood that this is not an embodiment, but is presented as an example. [Table 1-1] [Table 1-2]

[0029] The example information illustrated in Table 1 is the nature of the traffic associated with the application. The information can then be used to determine the quality of the infrequent smoke. This can help in identifying large data transfers and frequent small data transfers. In general, an Application Function (AF) is based on application layer signaling. or obtain service information from an application service provider (ASP) The AF creates a new session with the PCRF and notifies the PCRF of e.g. QoS requirements, Various session details may be provisioned, such as flow information, billing details, etc. If the session information changes at a later point in time, the AF sends these modifications to the PCRF. The aforementioned new additional session information may be used, for example, during initial session provisioning. It may be sent to the PCRF as a session modification request during or after the session modification request.

[0030] Figures 4-6, 8-11, and 13-14 (described below) show how to manage small data. 1 illustrates various embodiments of a method and apparatus for processing one or more The various steps being taken by the agent, server, and / or proxy The operations of the client, server, and proxy illustrated in these figures are shown. may represent logical entities in a communication network, and may be represented as in FIG. 15A or Such a network may have one of the general architectures shown in FIG. The software stored in the memory of a network node or device and running on its processor ( It is understood that the method may be implemented in the form of, for example, computer-executable instructions. 4-6, 8-11, and 13-14 may be implemented, for example, as shown in FIG. A network node or a computer system, such as the node or computer system shown in FIG. In the form of software (e.g., computer-executable instructions) stored in the memory of the device The computer-executable instructions may be implemented by a processor of a node or device. When executed, it performs the steps illustrated in the figures. The receiving step may include a processor of the node or device and a computer that executes the processor. Under the control of executable instructions (e.g., software), a node or device's communications circuitry (e.g., For example, this may be accomplished by circuits 34 or 97 of FIGS. 15C and 15D, respectively. It is understood.

[0031] Referring now to FIG. 4, an exemplary network 400 includes a bearer binding and event reporting BBERF 102, Policy and Charging Enforcement Function (PCEF) 104, Visit Policy Enforcement Function (PPA) 105, A home policy and charging rule function (V-PCRF) 106, a home policy and charging rule function ( H-PCRF)108, AF / SCS100, and Subscription Profile In some cases, for convenience, the V-PCRF 106 and The H-PCRF 108 generally corresponds to a PCRF, such as the PCRF 101 illustrated in FIG. The example network 400 is shown in simplified form to facilitate explanation of the disclosed subject matter. It should be understood that the above is merely an example and is not intended to limit the scope of the present disclosure. The devices, systems, and configurations may include, but are not limited to, networks, such as network 400. may instead be used to implement the embodiments disclosed herein, and all such Such embodiments are contemplated as being within the scope of the present disclosure. It should be understood that one or similar features may be repeated in the various figures to show the same or similar features.

[0032] FIG. 4 illustrates an exemplary call flow for session establishment. According to this, the initial provisioning or modification of session information by the SCS100 is By sending an Ameter AA-Request (AAR) message to the H-PCRF 108 , via the Rx interface. cy and charging control signaling flows and Quality of Service (QoS)parameter ma pping" describes the messages shown in FIG. 4, but does not include the steps shown in FIG. 2 and 7 are modified according to the embodiment shown.

[0033] Still referring to FIG. 4, at 1, a "trigger" event starts the flow. Examples of events that may cause the AS / SCS 100 to initiate this flow are provided as a limitation. These include, but are not limited to: AS / SCS100 or applications and UEs connected to the AS / SCS100 The properties of the data flow between them need to change. The AS / SCS100 or the applications connected to the AS / SCS100 Large files (e.g. software images, video clips, and audio clips) , new applications, etc.) to the UE. The AS / SCS100 or an application connected to the AS / SCS100 E. For example, this can be done by The application above is enabled, disabled, or moved to a new state. This can occur when The AS / SCS100 or an application connected to the AS / SCS100 Plan to increase or decrease the frequency of communication with E. For example, this could be Applications on E are enabled, disabled, or moved to a new state. This can occur when

[0034] In one embodiment, the AS / SCS 100 receives the subscription-id attribute value pair ( AVP) to the external identifier of the given UE, and the PCRF 106 may set, without limitation, H Each Home Subscriber Server (HSS) or User Subscriber Server (UDR), which may be collectively referred to as a SS / UDR, Query the UDR and get the external ID, e.g. IMSI or MSI The term "UE" refers to any node, e.g., M2M device or wireless device. It should be understood that the WTRU may refer to a wireless transmission / reception unit (WTRU). Both the session establishment procedure (FIG. 4) and an exemplary session modification procedure (not shown) In this case, the AF 100 uses the Diameter AAR message. When the AAR message is updated, it may contain the information listed in Table 1. The AR command is shown below.

[0035] (Example Updated AA-Request Message) Example message format:

number

[0036] In an exemplary embodiment, the new Grouped AVP includes the new information listed in Table 1. The AVP is defined for the AAR message as a separate AVP at the command level. In the sage or in the "Media-Component-Description" AV It can be contained within P.

[0037] 3GPP TS 29.214 “Policy and Charging Cont. As explained in the “Rx Reference Point for AF” -Application-identifier AVP (AVP code 504) It is of type OctetString and is the name of the specific AF service session to which it belongs. This information is used by the PCRF to identify the service. In one example, the new value can be used to differentiate the QoS for the different services. This AVP indicates to the PCRF that application-specific default values ​​should be used. For example, "XYZ_Electric_Measurement The value of "nt_App109" can be used. By way of example, this value is used for this type of application. This indicates to the PCRF that it should look for any locally configured values ​​for the application. , along with its associated flow information details, as a small data application. , may be configured in the PCRF.

[0038] The "Media-Component-Description" AVP can be used to According to an exemplary embodiment, it can be modified as shown below. The AVP is a newly added AVP according to one embodiment.

[0039] Example AVP format:

number

[0040] As shown above, the three example newly defined AVPs are "Media-Substitute It may be included as part of the "subflow-component" AVP and provide details for the subflow. The above example definition provides the bandwidth (BW) requirement of a flow over a certain duration. In one example, the PCRF may request a new bandwidth value after the time expires or The F100 can push these details to the PCRF after the time interval expires. Alternatively, for example, the Max-Requested-Bandwidth value and Durations can be grouped into a new AVP, and multiple instances of the new AVP can be The 'Traffic-Mode' AVP contains the current The mode of traffic may be indicated (e.g., as heavy or light or idle, etc.) for a given traffic. The network characteristics may be assigned based on, for example, the mode and application identifier. This can be done.

[0041] An example "Traffic-Characteristics" AVP is as follows: It can be defined. Example AVP format:

number

[0042] In an exemplary embodiment, the "Supported-Features" AVP is 0 has been amended to include an indication that it supports one or more new features, such as those mentioned above. It can be done.

[0043] Still referring to FIG. 4, in 7, according to the illustrated embodiment, AAA messages sent to the F100 may be, if necessary, treated as small data, e.g. It can be modified to inform the AF 100 about the flow that has been made. In some cases, the information provided in the AAR message by In this case, the PCRF can send a rejection and the PCRF can send a small data service The AF 100 may also be informed of acceptable values ​​for providing an updated The resulting AAA message is shown below.

[0044] Example message format:

number

[0045] A similar modification is required for the SCS100 and PCRF when a flow is re-admitted or reconfigured. It will be appreciated that this can be done for the RAR and RAA messages used by sea ​​bream.

[0046] Thus, as described above with reference to Table 1 and FIG. 4, a first node, e.g., S The CS 100 can provision the second node based on the trigger. The second node, e.g., PCRF, is responsible for the data flow and application The user can be provisioned with information associated with the application, thereby The second node may then use the information to deliver the information to the application or to The application can determine the rules for selecting the method that should be used to receive data from the application. The user equipment can host applications and the UE can The uplink data may be routed according to the following: As explained in, the rules can be, among others, Quality of Service (QoS). As will be described with reference to FIG. 4, the first node receives a The second node can then receive the Diameter message directly from the The second node may provision an observation associated with the data flow. When the observed behavior differs from the expected behavior, The second node may take an action (e.g., terminate the data flow, According to an exemplary embodiment, referring to Table 1, the diameter message The message includes the media type associated with the application, the application application identifiers, application bandwidth requirements, and application traffic behavior At least one of the associated parameters and the traffic type of the application The parameters may include, for example, but not limited to, The number of communications, the time delay between communications, the number of transmissions per communication session or per given duration The number of packets to be sent, the packet size, the duration for which the parameters apply, or the delay Further, as previously described, the trigger may be an application or a first An indication that the data rate associated with a node should change; The application or dataflow property associated with the first node needs to change. An indication of a data transfer event, or a notification of a data transfer event between the application and the first node. The communication may include an indication that the frequency of communication between the

[0047] According to an exemplary embodiment, referring to FIG. 5, a new interface, which may also be referred to as “T7”, The interface 502 communicates between the MTC-IWF 112 and the PCRF 101 in the MTC architecture. In one aspect, the AF is added to the PCRF 101 by the MTC-IWF and the Tsp Provision small data flow information through the interface. Another example On the visualization side, a new Diameter mechanism called Application Flow Information Request / Answer is introduced. The message carries this small data flow information on the Tsp and T7 interfaces. It is introduced to deliver

[0048] In some MTC scenarios, the SCS communicates with the service via the Tsp interface. The AF and PCRF may transmit service information to establish and maintain an AF session. Messages between the SCS and the MTC-IWF are sent via the Tsp interface. The MTC-IWF forwards this information to the appropriate PCRF. The MTC-IWF acts as a Diameter proxy towards the PCRF. It may take up a share or it may require a new interface with the PCRF (e.g. T7 or Rx').

[0049] Referring also to Figure 6, the SCS 100 creates or modifies session information with the PCRF 101. An example call flow for correcting a call from BBERF102, PCEF103, and 04, an exemplary network including an MTC-IWF 112, a PCRF 101, and an SCS 100 Illustrated is an exemplary network 600. The exemplary network 600 is provided to facilitate explanation of the disclosed subject matter. It is understood that the following description is simplified for illustrative purposes and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations may participate in a network, such as network 600. may also be used to implement the embodiments disclosed herein, All such embodiments are contemplated as being within the scope of this disclosure. It is understood that the same or similar features in the figures may be repeated in various figures to show the same or similar features in the figures. stomach.

[0050] Referring to Figure 6, 3 and 9, the application via the Tsp interface The Flow Information (AFI) request / answer messages are presented as an example, but not as a limitation. It may contain the following AVPs:

number

[0051] Referring to steps 5 and 8 in Figure 6, the application The session flow information request / answer messages are presented by way of example, but not by way of limitation, as follows: An example AVP on the T7 interface is external- Note that instead of id, the user-name AVP is used. The IWF 112 converts the external-id into an internal operator identification, such as an IMSI. It can be converted to the user-name, which is a child of the user.

number

[0052] Thus, as described above with reference to Figs. 5 and 6, a first node, e.g., SC The S100 can provision the second node based on the trigger. The second node, e.g., PCRF, is informed of the data flow and application by the first node. The second node may be provisioned with information associated with the To deliver information to an application or to receive information from an application A rule for selecting the method to be used for the first node can be determined. The Diameter message is sent to the MTC-IWF or the Service Capability Exposure Function. A second node can be provisioned by sending a Diameter messages are sent using the media type, application application identifier, application bandwidth requirements, application The parameters associated with the traffic behavior of the application and the traffic of the application The block may include at least one of the following block types:

[0053] Referring now to FIG. 7, in another exemplary embodiment, small data flow information is Instead of sending it to the CN via the C-IWF 112, the AS / SCS 100 The small data flow information can be stored directly in the UDR, so that the small data flow information is When a data flow is activated or a new bearer is configured, the PCRF or can be read by other core network nodes. The same messages mentioned above can be used. Figure 7 shows the same message as in 3GPP TR 23.8 62 “EPC enhancements to Support Interwork ing with Data Application Providers(MOSA The non-IMS AS illustrated in FIG. 7 may be an SCS. The HSS interface is provided by the SCS via the HSS-FE (HSS Front End). This can be used to provision small data flow information to the UDR. The PCRF then uses its Ud interface to transmit small data flow information. Can be read from UDR.

[0054] As described herein, small data flow information may include, for example, but not limited to, The PC may include various traffic characteristics of the flow, such as the number of packets, packet size, etc. The RF reads this information and determines which flows should be marked for small data. As an example, the purpose of having the AS / SCS provide traffic characteristics is to Let the S / SCS determine the small data and simply provide the flow information (5-tuple) Instead, the network, e.g., the PCRF, can be considered as the SD. The aim of the present invention is to enable the determination of

[0055] In one example, the AS / SCS uses the Mh interface to determine traffic characteristics. The UDR stores the data in the common user area. The UDR performs access control and determines which operations are permitted. During the IP-CAN session establishment, the PCRF checks whether The PCRF can query the UDR for associated traffic characteristics. During rule formation, traffic characteristic information can be used. The network PCC rules can be configured as described below, and the uplink The network PCC rules can be configured as described below. When updating flow information in the DR, the PCRF will, for example, notify all subscribers to be informed of the change. If the PCRF is subscribed to the EAP-TLS protocol, it may be notified of the changed data. The PCRF may then, where appropriate: The PCC rules may be amended.

[0056] (Applying small data flow information to downlink IP flows) Here, small data received by the PCRF from the AS / SCS according to an exemplary embodiment Looking at how new information can be applied within the network, the PCRF can When service information is received from the AS / SCS, PCC / QoS rules are formed and the existing The procedure can be used to send it to the PCEF / BBERF. PCC / QoS Rules In this case, the PCRF uses This may include new information, such as PCC rules or PCC rules that the PCRF sends to the PCEF. The RF sends the "Service Data Flow Filter" information in the QoS rule to the BBERF. In one aspect, the PCC rules can be implemented by modifying the Gx interface. The QoS rules are sent to the PCEF via the Gxx interface. Figure 2 shows the relationship between these interfaces in the PCC architecture. The interface is shown.

[0057] Network nodes such as PCRF, PGW, PCEF, and BBREF are ,Under the assumption that the data flow will comply with the,provisioned rules, Note that the network node may monitor each flow and determine the Detect whether the behavior differs from that provisioned by the AS / SCS. obtain.

[0058] As an example, if the behavior of an uplink flow differs from that configured by the AS / SCS, If so, it indicates that there is a problem with the device, that the device is at risk. In an example embodiment, the 3GPP core network node may: Initiates a message that terminates a flow and / or sends a message to the AS / SCS. Notifications can include an indication of what has been detected and the actions taken by the network. The message may include an action (e.g., termination) to inform the AS / SCS of the connection of the device. The notification may be sent to an intermediate party, such as the PCRF, the MTC-IWF, or the SCEF. It may be transmitted via the node.

[0059] As another example, the behavior of a downlink flow may differ from that configured by the AS / SCS. If so, it could be that someone is illegally accessing the device or using the device in an inappropriate manner. or initiating a denial of service attack. In an exemplary embodiment, the 3GPP core network node may It may initiate a message and / or a notification to be sent to the AS / SCS. An indication of what was detected and the action taken by the network (e.g., termination The message may include a notification to the AS / SCS to terminate the connection of the device. may be sent via an intermediate node such as a PCRF, an MTC-IWF, or an SCEF.

[0060] 8 and 9, the Gx reference point (PCRF-PCEF) is According to the form, the PCRF is modified to provide the small data information compiled by the PCRF to the PCEF. FIG. 8 shows the BBERF102, PCEF104, TDF114, and V-PCRF1. 06, H-PCRF 108, SPR 110, and OCS 116. FIG. 9 shows the BBERF102, PCEF104, TDF114, and V-PC An exemplary network 90 including an RF 106, an H-PCRF 108, and an OCS 116. 0. Exemplary networks 800 and 900 facilitate explanation of the disclosed subject matter. It will be understood that the following description is simplified for illustrative purposes and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations may be used in conjunction with networks 800 and 900, etc. In addition to or instead of a network, a network may be used to implement the embodiments disclosed herein. and all such embodiments are considered within the scope of this disclosure. In particular, reference numbers may be repeated in various figures to indicate the same or similar features in the figures. I want you to understand that.

[0061] Figures 8 and 9 show the Gx interface for PCC rule provisioning. 1 illustrates an example procedure that may be used to The pull data information is transported between the PCRF and the PCEF (P-GW). The procedure (provisioning requested by the PCEF 104) is shown in Figure 8. Referring to FIG. 8, the PCEF 104 uses the CC-Request message. In addition, small data information can be obtained from the PCRF. The new CC-Request message is explained below. In the illustrated example, The C-Answer message is used to provision the PCC rules. This message may be modified to include small data flow filters / information. An exemplary updated CC-Answer message according to an embodiment is as follows: The call flow shown in Figure 8 is generally based on 3GPP TS 29.213. Reproduced from 3, 3a, 3c, 12, 12a, 12d, 12e, and 12g. The messages in are modified according to the embodiment shown.

[0062] FIG. 9 illustrates an exemplary push delivery procedure (unsolicited provisioning) according to an exemplary embodiment. For example, during a PCRF-initiated IP-CAN session modification, the PCRF ,This procedure is used to provision PCC rules in the PCEF104 ( For example, it can be activated or deactivated or modified. The RA-Request message is sent from the PCRF to the PCEF as part of the This message may provision PCC rules. The RA-Request can be modified to include the filter / information. The call flow shown in FIG. Reproduced from GPP TS 29.213, 6, 6a, 6d, 6f, 8, 8a, The messages in 8b and 8d are modified according to the embodiment shown. do.

[0063] As mentioned above, various Diameter messages, such as CCR, CCA, and RAR, The page may be modified according to various embodiments. Additionally, the AVP may also be modified. An exemplary AVP that is modified in accordance with the present embodiment is underlined below. The "Supported-Features" AVP is a small data It can be modified to indicate information handling capabilities.

[0064] (Example CC-Request (CCR) command) Message Format:

number

[0065] As shown above, a new AVP, "Packet-Filter-Inform 'QoS-Information' AVP, 'QoS-Information' AVP, and 'Routing ng-Filter” AVP (“Routing-Rule-Install” AVP Some of them have been added to the RFC 2212 protocol, which can display small data packet filters / information.

[0066] (Example CC-Answer (CCA) Command) Example message format:

number

[0067] As mentioned above, the "Charging-Rule-Install" AVP and / or The "QoS-Information" AVP contains the information described in Table 1 of this specification and It can be modified to include small data flow filters / information such as filters and do. (Example Re-Auth-Request (RAR) command) Example message format:

number

[0068] Referring now to Figures 10 and 11, the Gxx reference point (PCRF-BBREF) is e.g. According to an exemplary embodiment, the PCRF provides the summarized small data information to the BBREF. FIG. 10 shows the BBERF 102, PCEF 104, and V-PCRF 10. 6, an H-PCRF 108, and an SPR 110. Figure 11 shows the BBERF102, PCEF104, V-PCRF106, and HP An exemplary network 1100 including a CRF 108 is shown. and 1100 have been simplified to facilitate explanation of the disclosed subject matter and are not intended to limit the scope of the present disclosure. It should be understood that the present disclosure is not intended to limit the scope of the present disclosure to other devices, systems, and The configuration may include, or may not include, networks such as networks 1000 and 1100. Instead, all such devices may be used to implement the embodiments disclosed herein. Various embodiments are contemplated as being within the scope of the present disclosure. It should be understood that may be repeated in various figures to show similar features.

[0069] Figures 10 and 11 show the Gxx interface for QoS rule provisioning. 1 illustrates an example procedure that may be used via the Small data information is transported between the PCRF and the BBERF 102. The communication procedure (provisioning requested by BBERF102) is shown in Figure 10. Referring to FIG. 10, the PCEF 104 receives the above-mentioned CC-Request message. The small data information can be obtained from the PCRF using the page shown in the figure. In the example, the CC-Answer message is sent to provision the QoS rules. This message has been modified to include small data flow filters / information. The call flow shown in FIG. It is reproduced from 3GPP TS 29.213, but 2, 2a, 2c, 8, 8a, The messages in 8c, 8d, and 8e are modified according to the embodiment shown. .

[0070] FIG. 11 illustrates an exemplary push delivery procedure (unsolicited provisioning) according to an exemplary embodiment. For example, during a PCRF-initiated IP-CAN session modification, Use this procedure to provision QoS rules in BBERF102. The tag can be changed (e.g., activated or deactivated or modified). RA-Request sent from PCRF to BBERF102 as part of the procedure The st message may provision QoS rules. The exemplary updated The RA-Request message is as described above. The call flow shown in FIG. is generally reproduced from 3GPP TS 29.213, with the exception of 2 and 2c. The message is modified according to the embodiment shown.

[0071] When the PCEF / BBERF receives the PCC / QoS rules as described above, it: Bearer binding is performed as specified in 3GPP TS 23.203, subclause 6.1.1.4. To support the small data flows / services described herein, Bearer binding feature is marked for small data in PCC / QoS rules The flows are considered and new bearers are created to support small data flows. It may be decided whether there is a need to use a bearer for the existing The function is available only when the small data filter rule is applied to the default bearer TFT or the dedicated bearer. It may also be determined whether the bare TFT can be included as part of the TFT. The small data coupling function is to integrate the use of small data with relevant entities (e.g. For example, the UE, S-GW, MME, etc.

[0072] According to an exemplary embodiment, a new QCI value is used for small data bearers. Exemplary QCI values ​​are set forth in Table 2 below. For example, the QCI values ​​are However, it can be used for small data bearers that may require low packet loss. As a further example, another QCI value may be delay tolerant but packet loss tolerant. It can be used for small data bearers with no overhead. [Table 2-1] [Table 2-2]

[0073] (Applying small data flow information to downlink IP flows) As an example, designating a bearer for small data may result in the entire data flow on the bearer being Rows can be considered small data. This can be useful in some scenarios, e.g. ,Scenarios involving non-MTC UE applications (e.g., chat applications) In these scenarios, some MTC devices In contrast, the network may, for example, mark specific IP flows rather than the entire bearer. A network may want only a set of IP flows to be considered as small data flows. In an exemplary embodiment, the network uses TFT to determine which IP flows are small data. This informs the UE which packets need to be considered for data transfer.

[0074] As background on TFT, in 3GPP networks, data traffic from UE is Data traffic is classified based on its QoS requirements and transmitted over different bearers. The classification of traffic is achieved with the help of TFT. TFT is a method to classify traffic based on IP flows or services. It contains a packet filter that can uniquely identify a service (a set of IP flows). A bearer can have one TFT associated with it. Default bearer The dedicated bearer may or may not have a TFT. In the "Activate Dedicated EPS Bearer Context Request" message, The default bearer is assigned in the "EPS Bearer Context Modification Request" message. The default EPS bearer context can be assigned a TFT. Does not have any TFTs assigned during the activation procedure (e.g., "default in the "Activate Default EPS Bearer Context Request" message. The modification of the TFT of the primary bearer is performed by specifying the bearer context in the "Modify EPS Bearer Context Request" message. This can be done by the core network during the AT&T correction procedure. A TFT has a set of all packet filters associated with a particular EPS bearer. There may be 16 packet filters. Each packet filter has a priority value, which is Must be unique among all packet filters in all TFTs associated with a PDN connection The UE must select the bearer with the highest priority to find the bearer on which data needs to be transmitted. In this paper, we evaluate all packet filters of all TFTs connected to the PDN. The following table 3 illustrates the current linkage of TFT using the Ara concept. An exemplary traffic flow chart, as defined in 24.008, section 10.5.6.12, is provided below. This indicates the TFT information element (IE). [Table 3] [Table 4]

[0075] Table 4 above shows a list of exemplary packet filters for TFT. According to the above, modifications are made to the TFT summarized above. Each packet filter in the packet filter list has two spare bits. In the embodiment, these spare bits are used for filtering small data packets, filtering normal packets, and filtering small data packets. Used to mark a particular packet filter as a An exemplary modified packet filter list is shown below (see Table 16): The TFT for the dedicated bearer and the TFT for the default bearer are modified in this way. For the modifications disclosed herein, There are several advantages.

[0076] For example, but not by way of limitation, a packet filter marked as "small data only" may The data is stored in the form of packets that are not evaluated during normal packet classification in connected mode. Therefore, they are not tied to a specific bearer but belong to a PDN connection. As a further example, a file marked as "Small Data Only" may be viewed as Packet filters are filtered out more quickly than packet filters marked as "normal" or "both". A general reserve value indicating the lowest priority will be "Small Data can be used for filters marked as "dedicated". At one time, by assigning a lower priority for "small data only" flows When the packet filter is matched for an uplink packet, the small device Matching for bearers marked for small data In connection mode, for example, ,The "small data only" packet filter may not be evaluated, and thus, The priority values ​​may not have any significance.

[0077] In an exemplary embodiment, packets marked as "small data only" or "both" The bit filter is evaluated by the UE during the transition from idle to connected mode. In some cases, a given UE may have uplink data to transmit and the UE When the UE is in idle mode, the UE first needs to transmit uplink data. It can determine a PDN connection based on the source IP address of the uplink data. After the PDN connection is determined, the UE may then The uplink data it has is stored as a "small device" in the TFT belonging to this PDN connection. Matches either the packet filter marked as "data only" or "both" If there is a match, according to an example embodiment, the UE may , instead of the normal service request procedure, a small data transfer procedure is performed. .

[0078] In one embodiment, a packet filter marked as "small data only" is For the purpose of identifying the bearer for transmitting data when E is already in connected mode During normal traffic flow classification, the UE does not evaluate Packet filters marked as "normal" or "both" are evaluated by the UE. The packet filters modified for small data are then filtered by the core network. Communicating to the UE during a bearer modification procedure or a dedicated bearer activation procedure According to an exemplary embodiment, a dedicated EPS bearer context activity The ESM message and the EMS message are , which is modified to carry an updated TFT IE, as described further below. In an exemplary embodiment, the TFT concept and a method for creating or modifying a TFT in a UE are described. The procedure remains the same, but the ESM messages are modified.

[0079] According to an exemplary embodiment, the existing TFT concept for identifying IP flows is For data, the core network uses a separate TFT to inform the UE which Can inform whether an IP flow should be considered as a small data flow As disclosed herein, a packet forwarding scheme for matching small data IP flows is A new small data TFT containing a Ket filter can be used. Referring to FIG. 1, according to the illustrated embodiment, the TFT is not a specific bearer, but a P TFT is linked to the DN connection, e.g. during the transition from idle to connected mode. A given UE first selects a PDN connection through which uplink data is transmitted. The UE then searches for the TFT in the PDN connection. Continuing with this example, if the SD TFT is per PDN connection, the UE first , you can search for packet data filter matches in the SD TFT (other TFTs If there is a match, the UE shall, instead of the normal service procedure, , perform the small data procedure. This determines whether the data is small data or not. This can reduce the number of transactions with the CN to identify the small data. The TFT is created by the network during PDN connection setup or during bearer modification process. They can be created dynamically through a procedure.

[0080] In an exemplary embodiment, the small data TFT transitions from idle mode to connected mode. Only during the row is evaluated by a given UE. Uplink data for the UE to transmit and when the UE is in idle mode, the UE first receives uplink data This can be done by the UE in the uplink debug mode. After the PDN connection is determined, e.g. The UE then checks whether a small data TFT is available for this PDN connection. If it is available, for example, the UE checks whether it has an uplink Determines whether the data matches any of the packet filters in this TFT. If there is a match, the UE proceeds with the normal service request procedure. In one embodiment, the "packet "Package Filter Evaluation Priority" determines the matching for packet filters in the SD TFT. The "Packet Filter Evaluation Priority" of the packet filter in the SD TFT is not used. The "priority" is relative to other packet filters in the TFT of other bearers belonging to this PDN connection. The "Packet Filter Evaluation Priority" value is not necessarily unique within the SD TFT. It can be set to a reserved value for the packet filter. The packet filters in the FT need to determine the bearers on which the UE needs to carry data. In this example case, the normal TFT monitor is not matched during connection mode. Switching can be done without considering the packet filters in the SD TFT.

[0081] According to various embodiments, the subscriber profile in the HSS / HLR / UDR is limited to The details can be updated with the following details, which are not included but are provided as an example: Whether and / or whether it is possible to carry out a pool data procedure whether all data from the UE is small data and the type of procedures allowed; Data plane (used to restrict UE to connecting to small data services only) and whether a PDN connection uses a small data plane; Should it be used?

[0082] During initial attach, the MME, S-GW, or P-GW shall 2 “Mobility Management Entity (MME) and S erving GPRS Support Node (SGSN) related "Interfaces based on Diameter Protocol" The above information is read together with the subscriber information in the insert subscriber data message, which will be described later. The above information is transmitted to the MME, S-GW, or P-GW via the small Also used to approve data connection requests and apply limits for small data services The MME, S-GW, or P-GW may, for example, send an attach accept message. This information may be passed to the UE in a message such as a ping message. The S-GW or P-GW routes the data via, for example, SMS, NAS messaging , delivered to / from the UE using small data delivery methods such as RRC messaging Alternatively, the MME, S-GW , or the P-GW may send a location update request, also as described in 3GPP TS 29.272. The message may be used to retrieve such information along with subscriber information.

[0083] Thus, in some cases, a device, for example a device equipped with an MME, may receive a first message. The first message may be received from the UE indicating that the UE is performing a small data procedure. The ATTACH request (see FIG. 1A) may include an indication of the support for the ATTACH request. In addition, the first message may indicate that the UE is using the small data procedure. The device may also send a second message to the network node. The second message may be received from a small data procedure, for example, an HSS. The second message may indicate one or more PDN connections that should use The type of small data procedure corresponding to each PDN connection may also be indicated. Based on the message, the device may respond to the first message. As will be explained, the response indicates that the UE has confirmed the small data procedure indicated in the second message. The adapter contains instructions to function in small data mode using one of the The device may then include a call response message (see FIG. 1A). The data may be delivered using one of the small data procedures available. The device also performs one of the small data procedures shown in the second message. In addition, the small data procedure may receive data from the UE according to NA This may be indicated via S messaging.

[0084] In another exemplary embodiment, the operator scans the subscriber profile into the SPR / UDR. The following are provided as examples, but are not limited to: The information can be structured in the SPR / UDR. Service and IP flow information that should be considered small data (service data flow) Low filter - see below). Small data traffic characteristics, e.g. packet size, packet frequency etc. Table 1 provides exemplary characteristics. PCC architecture elements (e.g., PCRF, PCE F, BBERF, and TDF) use this information to determine the small data flow. It is possible. AS / S that can provide small data information to the network (PCRF) The list of CSs and the information from the AS / SCS are provided to the PCRF by the SPR / UDR. A flag that indicates whether the information can be overridden. An example of this procedure is In one example, the PCRF may receive an S Only D information can be accepted.

[0085] In one example, the AS / SCS is retrieved by the PCRF and applied on the network. Small data information that may be retrieved can also be stored in the UDR. An example of this procedure is Similar configurations in the SPR are found in GPRS and UMTS networks. It should be understood that is also applicable.

[0086] As previously mentioned, the EMM and ESM messages may be modified in accordance with the exemplary embodiments. With reference to Table 5, the information elements of an exemplary Attach Request message are shown. The message indicates the UE's small data capability and that it is attached in small data mode. The request is modified to inform the MME. Therefore, as shown in Table 5 The Small Data Indication IE (see above) is added and the UE Network Capability IE is modified. In alternative embodiments, for example, "EPS Attach Type" or "MS Network Capability" may be used. Existing information elements such as "force" can be used to carry the small data indication. [Table 5]

[0087] Referring now to Table 6, the attach accept message is modified in accordance with an exemplary embodiment. The attach accept message, which may also be referred to as an attach response message, is sent when the UE: Of the small data procedures retrieved from the subscriber repository, e.g., HSS The instruction to operate in a small data mode using one of the following: or the response message is sent for the entire duration that the UE remains attached to the network. to inform the UE whether it should function in small data mode for The Small Data Indication IE may be added to the Attach Accept message. In an alternative embodiment, the small data instruction may be, for example, "EPS Attach Result" It can be added to an existing IE, such as the "spare half octet" of E. [Table 6]

[0088] Referring to Table 7, information elements of an exemplary PDN connectivity request message are shown. The message indicates that the network should mark the default bearer for small data. Therefore, as shown, the small data indication IE will be added. [Table 7]

[0089] Referring to Table 8, information elements of an exemplary bearer resource allocation request message are shown. This example message marks a dedicated bearer for small data and / or or a new small data IP flow filter. Therefore, as shown, a small data indication IE is added to The flow aggregate IE may be modified. [Table 8]

[0090] Referring to Table 9, information elements of an exemplary bearer resource modification request message are shown. This example message changes the small data marking status of a bearer. or the status of the small data IP flow packet filter Therefore, as shown, the small data indication IE , may be added and the Traffic Flow Aggregation IE may be modified. [Table 9]

[0091] Referring to Table 10, an exemplary default EPS bearer context activation request message The information elements of the message are shown in Figure 1. This exemplary message indicates that the default bearer is in standby. The RFC 2444 standard is amended to provide an indication of whether a LTE-2000 Routing Access Point should be considered as a data bearer or not. Therefore, a small data indication IE may be added, as shown. [Table 10]

[0092] Referring to Table 11, an exemplary dedicated EPS bearer context activation request message is The information elements of this message are shown. This exemplary message indicates that the dedicated bearer is a small data bearer. The amendment provides guidance on whether a product should be considered a maker. A small data indication IE may be added so that the TFT IE is This message also provides the small data packet filter to the UE. In one example, still referring to Table 11, the small data indication IE is If present in the message and indicates an SD bearer, all data on this bearer shall be D. As a further example, if a small data indication IE is present, And indicates a normal bearer, but if the TFT has a packet filter for small data If so, data that matches the packet filter is still considered small data. It will be possible. [Table 11]

[0093] Referring now to Table 12, information in an exemplary EPS Bearer Context Modification Request message is This exemplary message is for dynamic modification of bearers as SD bearers. or change the small data packet filter in the TFT. Thus, as shown, the small data indication IE may be modified to include the addition The TFT IE may be modified as described above. Referring to FIG. 2, a first node, for example, the SCS 100, may, based on a trigger, The second node, e.g., PCRF, can provision a second A node uses the information to deliver the information to the application or from the application. First, a rule for selecting the method to be used for receiving the Nodes provide the data flows and information associated with an application. The second node can be connected to a third node, e.g., a P-GW / PC. EF to deliver information to and from applications Provision rules to select the delivery method that should be used to receive The user equipment can host applications. Then, the third node sends a dedicated EPS bearer context activation request message or Rules for use by the UE using the modified EPC Bearer Context Request message In addition, a third node can distribute data flow information to the The third node may then compare the behavior of the second node with that of the first node, and the third node may then take an action associated with the comparison. It can be done (terminating the data flow or informing the second node of the result of the comparison). Alternatively, as mentioned above, the second node may The subscription database can be a database with a It can be provisioned via [Table 12]

[0094] New information elements (IEs) are disclosed herein and existing IEs are modified in various embodiments. Accordingly, it is amended herein. For example, the UE network capability IE may be modified to include small data This IE and the UE's IE may be modified to indicate the UE's capability to support the procedure. The complete definition of the coding details is given in 3GPP TS 24.301, clause 9.9.3.3. Section 4 “Non-Access-Stratum (NAS) protocol for The Evolved Packet System (EPS) is listed in Table 13. 1 illustrates an example of modified UE network capabilities according to an exemplary embodiment. Then, bit 7 of octet 7 (originally marked as spare) is marked by the UE as can be used to demonstrate its ability to support small data. . [Table 13]

[0095] The small data indication IE is used throughout this disclosure. The element informs, for a given UE, whether the UE should operate in small data mode. The small data indication information element shall be coded as shown in Tables 14 and 15. In one embodiment, the small data indication is a Type 1 information element. [Table 14] [Table 15]

[0096] As mentioned above, the packet filter list is part of the TFT IE. is defined in 3GPP TS 24.008, clause 10.5.6.12. Exemplary modifications to the filter list coding are shown in Table 16 below, and the exemplary modifications are: , are underlined. Table 17 shows exemplary packet filter type values, according to various embodiments. Shows. [Table 16] [Table 17]

[0097] Referring now to Figure 14, 3GPP TS 24.305 "Selective D isabling of 3GPP User Equipment Capabili ties (SDoUE) Management Object (MO)" This defines a management object that can be used to selectively enable and disable UE capabilities. According to an exemplary embodiment, the management object defines a small data flow capability. can be enabled and disabled. With reference to the depicted exemplary graphical user interface 1400, Objects communicate with each other via control plane messaging, such as NAS and RRC messaging. to enable and disable the transmission and reception of data packets. Leaf objects are used for control plane messaging such as NAS and RRC messaging. Through messaging, packets may be added to limit the number and frequency. The UE allows the user to transmit data packets via control plane messaging. A GUI that allows enabling and disabling transmission and reception, e.g. GUI 14 00. The GUI may include a packet It may also be possible to limit the number and frequency of the inputs. The GUI may also allow alternative parameters to be set, if desired. It should be understood that the present invention can be used to monitor and control the data. The GUI presents the user with a variety of charts or alternative visual depictions to help them make informed decisions. It should be understood that the GUI can provide a variety of information in a single GUI configuration. Based on the setting, the GUI may adjust leaf object settings or check other conditions. and extracts the leaf objects based on the GUI settings and the UE real-time operating conditions. For example, the GUI may be associated with an application that allows a user to It may be possible to limit the number of control plane messages that can be sent per The application may inform the UE that it has reached its limit for control plane messaging. When it detects this, it adjusts the leaf object's configuration and notifies the Later, for example, after a certain time has elapsed, the application may invalidate the data packet. The application again adjusts the control plane mechanism by adjusting the configuration on the leaf object. The data packet may be revalidated via messaging.

[0098] As mentioned above, the various techniques described herein may be implemented in hardware, firmware, It may be implemented in connection with software, or, where appropriate, with a combination of both. Such hardware, firmware, and software may be used in the communications network. The apparatus may reside in devices located at various nodes. The apparatus may also implement the methods described herein. As used herein, the terms "substitution" and "substitutions" may operate alone or in combination with one another to provide a In this case, the terms "apparatus," "network equipment," "node," "device," and "network "Work node" may be used synonymously.

[0099] FIG. 15A illustrates an example machine-to-machine ( M2M), Internet of Things (IoT), or Web of Things (WoT) communication systems Figure 10 is a schematic diagram of the IoT / WoT. In general, M2M technologies provide building blocks for IoT / WoT. It provides a single point of connection to any M2M device, M2M gateway, or M2M service platform. The layer can be a component of IoT / WoT as well as an IoT / WoT service layer. A client as shown in any of Figures 4-6, 8-11 and 13-14; Either the proxy or server device may be as shown in FIG. 15A-D. The communication system may include nodes such as:

[0100] As shown in FIG. 15A, the M2M / IoT / WoT communication system 10 includes a communication network. The communication network 12 includes a fixed network (e.g., EtherNet / IP). et, Fiber, ISDN, PLC, etc.), or wireless networks (e.g. The network may be a single network (e.g., WLAN, cellular, etc.) or a heterogeneous network. For example, communications network 12 may provide voice, data, video, messaging, broadcast, and other communications services. A network may consist of multiple access networks that provide content, such as a TV show, to multiple users. For example, the communications network 12 may be a Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), or Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA ), single-carrier FDMA (SC-FDMA), or other channel access methods. Further, the communication network 12 may include, for example, a core network, an internet Sensor Networks, Industrial Control Networks, Personal Area Networks, Fusion Personal network, satellite network, home network, or corporate network, etc. Other networks may also be included.

[0101] As shown in FIG. 15A, the M2M / IoT / WoT communication system 10 includes an infrastructure The infrastructure domain may include a structure domain and a field domain. The domain refers to the network side of an end-to-end M2M deployment, and the field domain refers to the Usually refers to the area network behind the M2M gateway. Field domain and Both the infrastructure domain and the network domain are managed by the various different nodes of the network (e.g. For example, a field domain may include: The M2M gateway 14 may include an M2M gateway and an end device 18. The M2M / IoT / WoM device 14 and the M2M terminal device 18 can be connected to the M2M / IoT / WoM network as desired. It will be understood that the M2M gateway device may be included in the communication system 10. Each of the M2M terminal devices 14 and 18 is connected to the communication network 12 or a direct wireless link. The M2M gateway device is configured to transmit and receive signals via the link. The system 14 supports wireless M2M devices (e.g., cellular and non-cellular) as well as fixed networks. A network M2M device (e.g., PLC) communicates with an operator network such as a communication network 12. It is possible to communicate either through a network or through a direct wireless link. For example, the M2M device 18 may collect data and communicate with the communication network 12 or The data is sent to the M2M application 20 or the M2M device via a direct wireless link. The M2M device 18 may also transmit to the M2M application 20 or M2M The data and signals may be received from the M device 18. In this way, the M2M application 20 is connected to the M2M service platform 22. The M2M device 18 and the gateway 14 may, for example, For example, cellular, WLAN, WPAN (e.g., Zigbee (registered trademark), 6LoWP Various types of wireless technologies, including AN, Bluetooth®, direct wireless links, and wired Exemplary M2M devices include tablets, smartphones, and Applications include medical devices, temperature and weather monitors, connected cars, smart meters, and gaming. Consoles, personal digital assistants, health and welfare monitors, lights, thermostats, appliances , garage doors, and other actuator-based devices, security devices, As well as smart outlets, but are not limited to these.

[0102] The term "service layer" refers to a functional layer within a network service architecture. The service layer typically implements application protocols such as HTTP, CoAP, or MQTT. It sits above the protocol layer and provides value-added services to client applications. The service layer also provides interfaces to, for example, the control layer and the transport / access layer. The service layer provides the service to the core network in the lower resource layer such as the access layer. Service definition, service runtime activation, policy management, access control, and service classes Support multiple categories of (service) capabilities or functionality, including pinging. Several industry standards bodies, e.g., oneM2M, have developed standards for Internet / Web, cellular, M2M type devices and applications for deployment in home, enterprise, and residential networks Developing an M2M service layer to address the challenges associated with integrating The M2M service layer provides applications and / or various devices with or the capabilities or functionality supported by a service layer, which may be referred to as an SCL. In some examples, the restriction Although not a common feature, it can be used by a variety of applications, such as security, billing, etc. , data management, device management, discovery, provisioning, and connectivity management. These capabilities or functionalities are implemented in the message formats defined by the M2M service layer. Such various types are exposed through an API that utilizes mats, resource structures, and resource representations. CSE or SCL shall not grant them such capabilities. or by hardware and / or software to use the functionality may be implemented and exposed to a variety of applications and / or devices. (Service) A functional entity that provides a capability or functionality (e.g., such a function A functional interface between entities.

[0103] Referring to FIG. 15B, the illustrated M2M service layer 22 in the field domain includes: M2M application 20, M2M gateway device 14, and M2M terminal device The M2M service layer provides services for the device 18 and the communication network 12. 22 may include any number of M2M applications, M2M gateway devices, It will be understood that the M2M terminal device 18 and the communication network 12 may communicate with each other. The M2M service layer 22 may be implemented by one or more servers, computers, etc. The M2M service layer 22 may be implemented in the M2M terminal device 18, the M2M gateway providing service capabilities that are applied to devices 14 and M2M applications 20 The function of the M2M service layer 22 is, for example, to provide services to the cellular core network as a web server. The method may be implemented in a variety of ways, such as on the network, in the cloud, etc.

[0104] Similar to the illustrated M2M service layer 22, the M2M service layer 22 is implemented in the infrastructure domain. The M2M service layer 22' is in the infrastructure domain. and services for the M2M application 20' and the underlying communication network 12'. The M2M service layer 22' also provides an M2M gateway in the field domain. It also provides services for the device 14 and the M2M terminal device 18. The service layer 22' may include any number of M2M applications, M2M gateway devices, and It will be understood that the M2M service layer 22' may communicate with the M2M terminal device. M2M service layer 2 can interact with service layers from different service providers. 2' is one or more servers, computers, virtual machines (e.g., cloud / computing / storage The present invention may be implemented by a software application (eg, a server), a service provider (eg, a software company), or the like.

[0105] Still referring to FIG. 15B, the M2M service layers 22 and 22′ are A core set of service delivery capabilities that applications and verticals can leverage These service capabilities are provided by M2M applications 20 and 20'. It interacts with devices and performs data collection, data analysis, device management, security, billing, and service Essentially, these service capabilities allow This removes the burden of implementing these functionalities from the application, thus Simplify application development and reduce cost and time to market. Service Layer 22 and 22' also include a service layer 22 and and 22' in connection with the services provided through the various networks 12 and 12'. It also enables communication.

[0106] M2M applications 20 and 20' include, but are not limited to, transportation, health and welfare , connected home, energy management, asset tracking, and security and surveillance, etc. As mentioned above, the devices, gateways, and The M2M service layer, which runs across the M2M servers and other servers, handles e.g. data collection, data Device management, security, billing, location tracking / geofencing, device / service issuance It supports functions such as monitoring, legacy system integration, and provides these functions as a service. M2M applications 20 and 20'.

[0107] Generally, service layers such as service layers 22 and 22' shown in FIGS. 15A and 15B The Service Layer (SL) provides the Application Programming Interface (API) and Supporting value-added service capabilities through a set of layer networking interfaces Define the software middleware layer. ETSI M2M and oneM2M architecture Both of these architectures define a service layer. The ETSI M2M service layer is the service The SCL is the ETSI M2M architecture for various different nodes. For example, the service layer instantiation can be implemented in the M2M device (device Device SCL (DSCL), Gateway SCL (GSCL ) and / or network nodes (Network SCL (NSCL) The oneM2M service layer can be implemented within the Common Service Functions (CSF ) (i.e., service capabilities) of one or more specific types of CSFs. The instantiation of the set can be done on different types of network nodes (e.g. infrastructure Common services that can be hosted on any one of several nodes (channel nodes, intermediate nodes, application specific nodes) The third generation partnership project (3 GPP) also defines an architecture for machine type communications (MTC). In that architecture, the service layer and the service capabilities it provides are It is implemented as part of the Data Center Server (SCS) of the ETSI M2M architecture. L, GSCL, or NSCL, service capability support of 3GPP MTC architecture in the SCS, in the CSF or CSE of the oneM2M architecture, or in the network. The service layer instance is instantiated on a different node in the network, regardless of whether it is instantiated on another node in the network. The services provided by the Company include servers, computers, and other computing devices or nodes. on one or more standalone nodes in the network, or on one or more existing nodes A logical entity (e.g., software, computer As an example, a service layer or a component thereof may be implemented as a service layer. 15C or 15D, which are described below. The network node (e.g., a sub-node) has the general architecture shown in FIG. It is implemented in the form of software that runs on a server, computer, gateway, device, etc. It can be equipped with

[0108] Further, the methods and functionality described herein may be implemented in, for example, the above networks and Service-oriented architecture for accessing services such as application management services M using SOA and / or Resource Oriented Architecture (ROA) It may be implemented as part of a 2M network.

[0109] FIG. 15C illustrates an M2M network such as that illustrated in FIGS. 15A and 15B. It can act as an M server, gateway, device, or other node. -11, and 13-14 of the client, server, or proxy shown in 1 is a block diagram of an exemplary hardware / software architecture for a node of such a network; As shown in FIG. 15C, a node 30 includes a processor 32 and a a transmitter 34, a transmission / reception element 36, a speaker / microphone 38, a keypad 40, Display / touchpad 42, non-removable memory 44, and removable memory 46, a power supply 48, a Global Positioning System (GPS) chipset 50, and other peripherals. 52. The node 30 may also include communication elements such as a transceiver 34 and a transmit / receive element 36. Node 30 may include any of the subcomponents of the preceding elements while remaining consistent with the embodiment. It will be understood that the nodes may include any combination of the nodes described herein. It may be a node that implements small data functionality.

[0110] The processor 32 may be a general purpose processor, a special purpose processor, a conventional processor, a digital Digital Signal Processor (DSP), multiple microprocessors, associated with a DSP core One or more microprocessors, controllers, microcontrollers, application specific processors Application-Specific Integrated Circuits (ASIC), Field Programmable Gate Array (FPGA) circuits, any It may be another type of integrated circuit (IC), a state machine, etc. The processor 32 is The node 30 may be configured to perform a variety of functions, including: The processor 32 may perform any other functionality that enables the transmission / reception element 15C shows a block diagram of a processor 32 and a transceiver 34 which may be coupled to a processor 32 and a transceiver 36. Although the transceiver 34 is depicted as a separate component, the processor 32 and the transceiver It will be appreciated that 34 may be integrated together in an electronic package or chip. The processor 32 may include an application layer program (e.g., a browser) and / or Processor 3 may perform radio access layer (RAN) programming and / or communications. 2. Authentication, security, etc., at the access layer and / or application layer, etc. Security operations such as key agreement and / or encryption operations may be performed.

[0111] As shown in FIG. 15C, the processor 32 may include its communication circuitry (e.g., a transceiver 34 and transmit / receive element 36). Through execution of the command, node 30 communicates with other nodes through the network to which it is connected. Specifically, the processor 32 may control the communication circuitry to transmit the 5-16, 18-22, and 24) as described herein and in the claims. 15C shows a block diagram of a processor 32 that may control a communication circuit to perform the steps of receiving and transmitting a signal. Although the processor 32 and the transceiver 34 are depicted as separate components, It will be appreciated that the receiver 34 may be co-integrated in an electronic package or chip. Wax.

[0112] The transmitting / receiving element 36 communicates with other nodes, including M2M servers, gateways, devices, etc. The device may be configured to transmit signals to or receive signals from, for example: In an embodiment, the transmit / receive element 36 is configured to transmit and / or receive RF signals. The transmit / receive element 36 may be an antenna configured for WLAN, WPAN, cellular, etc. In an embodiment, the present invention may support a variety of networks and air interfaces. The transmitting / receiving element 36 may, for example, transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, the transmitter / detector may be configured to receive. / Receiving element 36 may be configured to transmit and receive both RF and optical signals. The transmit / receive element 36 may transmit and / or receive any combination of wireless or wired signals. It will be appreciated that the can be configured to receive.

[0113] In addition, the transmit / receive element 36, although depicted in FIG. 15C as a single element, may be a Node 30 may include any number of transmit / receive elements 36. More specifically, node 30 may include: MIMO technology may be employed. Thus, in an embodiment, the node 30 transmits wireless signals and two or more transmit / receive elements 36 (e.g., multiple antennas) for receiving obtain.

[0114] The transceiver 34 is adapted to modulate the signals transmitted by the transmit / receive element 36, and and may be configured to demodulate the signal received by the transmit / receive element 36. Additionally, node 30 may have multi-mode capabilities. 30 communicates via multiple RATs, e.g., UTRA and IEEE 802.11. The wireless communication system may include multiple transceivers to enable communication between the wireless communication system and the wireless device.

[0115] The processor 32 may include a non-removable memory 44 and / or a removable memory 46. The information may be accessed from and data may be stored in any type of suitable memory, such as a non-volatile memory. The removable memory 44 may be a random access memory (RAM), a read-only memory ( The memory may include a ROM, a hard disk, or any other type of memory storage device. The removable memory 46 may be a subscriber identity module (SIM) card, a memory stick , a secure digital (SD) memory card, etc. In another embodiment, the processor 32 is a memory that is not physically located on the node 30, such as on a server or a home computer. The processor 32 may access information from and store data in the UE (e.g., , GUI 1400), specifically, the lower layer network that communicates with the UE, the application displays or indicators to reflect the status of your application or other services. The processor may be configured to control the lighting patterns, images, or colors on the monitor 42. The power supply 32 may receive power from a power source 48 and may provide power to other components within the node 30. The power source 48 may be configured to distribute and / or control the power to the node 30. For example, power source 48 may be one or more dry cell batteries. (e.g. nickel cadmium (NiCd), nickel zinc (NiZn), nickel water These may include lithium-ion (NiMH), lithium-ion (Li-ion), solar cells, fuel cells, etc. do.

[0116] The processor 32 also receives location information (e.g., longitude and Node 3 may be coupled to a GPS chipset 50 configured to provide a GPS coordinate system (GNSS) and latitude. 0 may obtain location information via any suitable location determination method while remaining consistent with an embodiment. It will be understood that it is possible to obtain

[0117] The processor 32 may further include additional features, functionality, and / or wired or wireless connections. It includes one or more software and / or hardware modules that provide For example, the peripherals 52 may be accelerometers, e-computers, AMPUS, satellite transceiver, sensor, digital camera (for photo or video), universal Serial bus (USB) port, vibration device, TV receiver, hands-free headset , Bluetooth® module, Frequency Modulation (FM) radio unit , digital music players, media players, video game player modules, interfaces - It may include a web browser, etc.

[0118] FIG. 15D illustrates an M2M network such as that illustrated in FIGS. 15A and 15B. It can act as an M server, gateway, device, or other node. -11 and 13-14, such as the client, server, or proxy An exemplary computing device that may also be used to implement one or more nodes of a network. 1 is a block diagram of a computing system 90. or a server, primarily where such software is stored or accessed. or by any other means, computer readable information, which may be in the form of software. Such computer-readable instructions may be used to The operating system 90 may be executed within a central processing unit (CPU) 91. Many known workstations, servers, and personal computers use The central processing unit 91 is implemented by a single chip CPU called a microprocessor. In other machines, the central processing unit 91 may include multiple processors. 1 is a processor that performs additional functions or assists CPU 91, distinct from the main CPU 91; The CPU 91 and / or the co-processor 81 may E2E M2, such as receiving a certificate or authenticating based on a session certificate Receiving data related to the disclosed systems and methods for M-service layer sessions , generated, and processed.

[0119] In operation, the CPU 91 fetches, decodes, and executes instructions and provides the primary device of the computer. The information is transferred to and from other resources via a system bus 80, which is a data transfer path. Such a system bus transfers data from the components in the computing system 90. The system bus 80 typically connects the various components of the system and defines the medium for data exchange. , a data line for transmitting data, and an address line for transmitting an address. , control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) It's a bus.

[0120] The memory devices coupled to the system bus 80 include random access memory (RAM), 82 and a read only memory (ROM) 93. Such memory is used to store information. ROM 93 generally includes circuitry that allows the ROM to be written and read. The data stored in the RAM 82 includes data that cannot be read from the CP It cannot be read or changed by the U91 or other hardware devices. Access to the RAM 82 and / or ROM 93 is controlled by the memory controller 92. When an instruction is executed, the memory controller 92 assigns a virtual address to the The memory controller 92 may provide an address translation function to convert the address into a physical address. Also, it provides a mechanism to isolate processes within a system and isolate system processes from user processes. This provides a memory protection function. Therefore, a program that runs in the first mode can automatically A process can only access memory that is mapped by its own process virtual address space. The virtual address space of another process cannot be accessed unless memory sharing between processes is configured. The memory in the memory cannot be accessed.

[0121] In addition, the computing system 90 includes a CPU 91, a printer 94, a keyboard, The PLC is responsible for communicating commands to peripheral devices such as the keyboard 84, mouse 95, and disk drive 85. It may include some peripheral controller 83 .

[0122] The display 86 controlled by the display controller 96 is It is used to display the visual output generated by the display system 90. The visual output may include text, graphics, animated graphics, and video. Display 86 can be a CRT-based video display, an LCD-based flat panel display, or a Panel display, gas plasma based flat panel display, or touch The display controller 96 may be implemented with a display 86. The video input / output (VOUT) section contains the electronic components required to generate the video signal that is to be transmitted.

[0123] Further, the computing system 90 is 15A and 15B to enable communication with other nodes in the network. Connecting the computing system 90 to an external communications network such as the network 12 For example, a network adapter 97 may be used for communication. The circuit may be used alone or in combination with a CPU 91 (e.g., Figs. 4-6, 8-11, and 13-14) the transmitting and receiving steps as described herein and in the claims. It can be used to perform the following:

[0124] Any of the methods and processes described herein may further comprise instructions for executing a program on a computer. , executed by machines such as servers, M2M terminal devices, M2M gateway devices, etc. may be used to implement and / or process the systems, methods, and processes described herein. Implementing computer-executable instructions stored on a computer-readable storage medium It is understood that the present invention may be embodied in the form of instructions (i.e., program code). Any of the steps, operations, or functions described above may be implemented in accordance with such The computer-readable storage medium may be implemented in the form of computer-executable instructions. Volatile and non-volatile transactions implemented in any method or technology for storage of information. This includes both removable and non-removable media, but is not limited to such computer readable media. A computer-readable storage medium does not include a signal. A computer-readable storage medium includes a RAM , ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital Multi-purpose discs (DVDs) or other optical disk storage devices, magnetic cassettes, magnetic Tape, magnetic disk storage device or other magnetic storage device, or Any computer-accessible This includes, but is not limited to, other physical media.

[0125] In describing the preferred embodiments of the subject matter of the present disclosure as illustrated in the figures, specific The technical terminology is employed for the sake of clarity. However, claimed subject matter is not limited to such There is no intent to be limited to the specific terminology selected, and each specific element may accomplish a similar purpose. It is to be understood that the present invention includes all technical equivalents that operate similarly to the above-mentioned embodiments.

[0126] Below is a list of acronyms related to Service Level Technology that may appear in the descriptions above: Unless otherwise specified, the acronyms used herein are abbreviated to the corresponding acronyms listed below. This refers to a term that AAA AA-Answer AAR AA-Request AF Application Features APN Access Point Name AS Application Server ASP Application Service Provider AVP attribute value pairs BBERF Bearer Binding and Event Reporting Function CN Core Network DRB Data Radio Bearer EMM EPS Mobility Management eNB Evolved Node B EPS Evolved Packet System ESM EPS Session Management GPRS General Packet Radio Service GTP GPRS Tunneling Protocol GTP-C GTP control GTP-U GTP User HSS Home Subscriber Server MME Mobility Management Entity MO Managed Object MT Mobile is out MTC Machine Type Communication MTC-IWF Machine Type Communication-Interworking Function NAS non-access layer PCC Policy and Charging Control PCEF Policy and Charging Enforcement Function PCRF Policy and Charging Rules Function PDN Packet Data Network P-GW PDN Gateway RAA Reauthorization Answer (RA-Answer) RAR Reauthorization Request (RAR) SCEF Service Capability Exposure Function SCS Service Capabilities Server SD Small Data SDDTE Small Data and Device Trigger Extension S-GW Serving Gateway SPR Subscription Profile Repository SRB Signalling Radio Bearer TA terminal compatibility TAU Tracking Area Update TDF Traffic Detection Function TE Terminal Equipment TFT Traffic Flow Template UDR User Data Repository UE User Equipment UICC Universal Integrated Circuit Card

[0127] This written description is provided to disclose the invention, including the best mode, and also to enable any person skilled in the art to understand any disclosed embodiments. To make and use the device or system, and to perform any incorporated method The following examples are provided to enable the invention to be practiced, including: The scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other embodiments are to be construed as including structural elements that do not differ from the literal terms of the claims. or equivalent structural elements that differ only insignificantly from the literal terms of the claim. are intended to be within the scope of the claims.

Claims

1. An apparatus comprising a processor and a memory, the apparatus further comprising computer-executable instructions stored in the memory, the instructions, when executed by the processor, sending a first indication to a network entity that the device supports one or more small data procedures; receiving from the network entity a second indication that the device may use a first small data procedure of the one or more small data procedures and a third indication that uplink data is transmitted using only the first small data procedure; transmitting the uplink data to the network entity using the first small data procedure; An apparatus for causing the apparatus to perform the above.

2. The device described in claim 1, wherein the first instruction is sent in a first message, the second instruction is received in a second message, and the third instruction is received in a third message.

3. The device of claim 1, wherein the second instruction and the third instruction are received at different times.

4. The device of claim 1, wherein the first instruction is sent within a first message, and the second instruction and the third instruction are received within a second message.

5. The device of claim 1, wherein the second instruction and the third instruction are received within an attach acceptance message.

6. The apparatus of claim 1, wherein the one or more small data procedures are indicated via non-access stratum (NAS) messaging.

7. A method performed by an apparatus, comprising: sending a first indication to a network entity that the device supports one or more small data procedures; receiving from the network entity a second indication that the device may use a first small data procedure of the one or more small data procedures and a third indication that uplink data is transmitted using only the first small data procedure; transmitting the uplink data to the network entity using the first small data procedure; A method comprising:

8. The method described in claim 7, wherein the first instruction is sent in a first message, the second instruction is received in a second message, and the third instruction is received in a third message.

9. The method of claim 7, wherein the second instruction and the third instruction are received at different times.

10. The method of claim 7, wherein the first instruction is sent in a first message and the second instruction and the third instruction are received in a second message.

11. The method of claim 7, wherein the second instruction and the third instruction are received within an attach acceptance message.

12. The method of claim 7, wherein the one or more small data procedures are indicated via non-access stratum (NAS) messaging.

13. A network entity comprising a processor and a memory, the network entity further comprising computer-executable instructions stored in the memory, the instructions, when executed by the processor, receiving a first indication from a device that the device supports one or more small data procedures; transmitting to the device a second indication that the device may use a first small data procedure of the one or more small data procedures and a third indication that uplink data is transmitted using only the first small data procedure; receiving the uplink data from the device based on the first small data procedure; A network entity that causes the network entity to perform the following:

14. A network entity as described in claim 13, wherein the first instruction is received in a first message, the second instruction is sent in a second message, and the third instruction is sent in a third message.

15. The network entity of claim 13, wherein the first instruction is received in a first message and the second instruction and the third instruction are sent in a second message.

16. The network entity of claim 13, wherein the second instruction and the third instruction are transmitted within an attach acceptance message.

17. A method performed by a network entity, comprising: receiving a first indication from a device that the device supports one or more small data procedures; transmitting to the device a second indication that the device may use a first small data procedure of the one or more small data procedures and a third indication that uplink data is transmitted using only the first small data procedure; receiving the uplink data from the device based on the first small data procedure; A method comprising:

18. The method of claim 17, wherein the first instruction is received in a first message, the second instruction is sent in a second message, and the third instruction is sent in a third message.

19. The method of claim 17, wherein the first instruction is received in a first message and the second instruction and the third instruction are transmitted in a second message.

20. The method of claim 17, wherein the second instruction and the third instruction are transmitted within an attach acceptance message.

Citation Information

Patent Citations

  • Small data communication in wireless communication networks

    JP2014523181A

  • Communication protocol for short data transmissions

    WO2014097223A2