Admission control for early data transmission

Abstract

To provide a core network device, a base station device, a terminal device, and a method for supporting early data transmission (EDT) of a terminal device.SOLUTION: In a communication system, a user terminal includes receiving means for receiving, from an access network node, a parameter indicating whether a user terminal is restricted or authorized to transmit user data in messages transmitted on an uplink synchronization channel (UL-SCH), and a hardware processor that processes an instruction for determining whether transmission of user data in a message is restricted or authorized on the basis of the parameter.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] This disclosure relates to communication systems. It is particularly, but not exclusively, related to wireless communication systems and devices thereof that operate in accordance with 3rd Generation Partnership Project (3GPP) standards or equivalents or derivatives thereof. It is particularly, but not exclusively, related to admission control of early data transmission (EDT) in so-called "next generation" systems. [Background technology]

[0002] 3GPP working groups are discussing the introduction of an EDT feature for Rel-15 enhanced machine-type communication (eMTC) and narrowband-based Internet of Things (NB-IoT). This feature enables user equipment (UE) to transmit small data in Radio Resource Control (RRC) Message 3 (Msg3: a message transmitted on the uplink synchronization channel (UL-SCH) as part of the random access procedure, containing a Cell Radio Network Temporary Identifier (C-RNTI), Media Access Control Element (MAC CE), or Common Control Channel Service Data Unit (CCCH SDU) sent from higher layers and associated with the UE contention resolution identity, using control and user plane cellular over IoT (CIoT) enhanced packet system (EPS) optimizations). In the following, MsgX generally refers to step X of the contention-based random access procedure (see Figure 1 (TA36.300, Figure 10.1.5.1-1)). For example, the message denoted "Msg3" is the first scheduled uplink (UL) message for the grant provided by the random access response (RAR) message. Normal downlink (DL) / UL transmissions can occur after the random access procedure.

[0003] The agreement of the 3GPP RAN2 Working Group to date has been communicated in LS R2-1711978 / S2-177180.

[0004] [Table 1] RAN2#99 Agreement -The aim is to support early UL data transmission in Msg3 for control plane and user plane CIoT EPS optimization. -The aim is to support early DL data transmission in Msg4 for control plane and user plane CIoT EPS optimization. - Early data transmission functionality is considered if AS security is not established only for data transmission using CP. - Early data transmission functionality is considered if AS security has not been established for data transmission using CP and / or UP.

[0005] 3GPP RAN2 further discussed the details of EDT functionality and agreed on the following in RAN2#99bis:

[0006] [Table 2] RAN2#99bis Agreement -EDT is intended to be used for data, not for NAS signaling. - RAN2 considers that the S-TMSI in the CP and the resumeID and shortResumeMAC-I solutions in the UP are sufficient to identify the UE at the MME and eNB, respectively. In the CP solution, the NAS PDU for data is encapsulated in the RRC message sent in Msg3 and transmitted as a CCCH SDU. - In the CP solution, NAS PDU data in DL can optionally be encapsulated in RRC messages sent in Msg4 and transmitted as CCCH SDUs. - In the UP solution, SRB0 is used to send the RRC message in Msg3. In the UP solution, AS security is resumed before sending Msg3, and the data sent in Msg3 is protected by AS security. - In the UP solution, DL data can optionally be multiplexed onto MAC, i.e. DCCH (RRC messages) and DTCH (UP data) in Msg4. - Msg4 determines whether the UE is in RRC connected mode or RRC idle mode. The content of Msg4 for EDT is FFS. - If you need to put in place an authorization mechanism, it is FFS. - For FFS:UP solution: In case of pinning, i.e. CCCH (RRCConnectionResumeReq) + DCCH (NAS PDU via pinning).

[0007] As mentioned above, RAN2 is intended to support early UL data transmission in Msg3 for CIoT Enhanced Packet System (EPS) optimization of the control plane and user plane.

[0008] According to current procedures, the transmission of Msg3 is performed based on the initial UL grant provided by the RAR, and therefore the size of the transport block depends on the grant. If an uplink transmission is required, e.g. in contention resolution, the enhanced Node B (eNB) should not provide a grant of less than 56 bits in the RAR (88 bits for NB-IoT) (see TS 36.300).

[0009] Msg3 and Msg4 (contention resolution) (see Figure 1) use the Hybrid Automatic Repeat Request (HARQ) process. According to the current specification, Msg3 carries at least the Non-Access Stratum (NAS) UE identifier for initial access, but does not carry NAS messages. Msg3 transmission is done using a separate Msg3 buffer (which has higher priority than the UL buffer).

[0010] Control Plane (CP) CIoT EPS Optimization Early Data Transmission

[0011] An exemplary call flow that allows sending data in Msg3(UL) and / or Msg4(DL) as NAS protocol data units (PDUs) is shown in Figure 2. The procedure is briefly described below.

[0012] A. Resource Determination: The eNB5 decides to allow early transmission of small data packet sizes without establishing a full RRC connection. The eNB5 allocates Physical Random Access Channel (PRACH) resources for this purpose. 0. The eNB5 broadcasts resources using a system information broadcast (SIB). B. The UE 3 selects a PRACH resource based on the broadcasted resources and the amount of data to transmit, which may be based on a random selection from the corresponding PRACH pool.

[0013] Note: If in the Msg3 procedure PRACH resources are not broadcast in Msg0 for data, or if the UE3 intends to perform a NAS signaling procedure, or if the UE3 intends to send or receive more data than is possible in one Medium Access Control (MAC) block, the UE3 uses the legacy RRC connection establishment / resumption procedure.

[0014] 1. The UE 3 transmits a properly formatted PRACH preamble (Msg1: Random Access Preamble). 2. UE3 receives the RAR (Msg2). In current Long Term Evolution (LTE), the RAR may include an uplink grant and a timing advance (TA) (in addition to a temporary C-RNTI, etc.). To enable data transmission in Msg3, the RAR may be updated to include power control information. Otherwise, UE3 may use open-loop power control (i.e., UE3 determines the transmit power itself). 3. UE3 sends a properly formatted Msg3 with the UL grant indicated in the RAR, along with the UE identifier (UEID) (see below) and a NAS PDU. UE3 takes into account the power control information from the RAR, if included. UE3 starts a contention resolution timer after this step. 4-6. The eNB 5 selects an appropriate mobility management entity (MME) 9 based on the UE ID and forwards the NAS PDU to the selected MME 9. The eNB 5 may indicate to the MME 9 that the UE 3 has initiated the EDT procedure. If DL data for the UE 3 is available, the serving gateway (SGW) 11 provides the downlink data to the MME 9, which forwards the downlink data as a NAS PDU to the eNB 5, which passes the NAS PDU to the UE 3. If the eNB indicates that the UE 3 has initiated early data transmission, the MME 9 may accordingly be configured to terminate the associated S1-AP connection after forwarding any downlink NAS PDUs. This indicator may be used by the MME 9 to prioritize the processing of UL data and expedite step 6. 7. The network acknowledges receipt of Msg3, completes contention resolution, and responds with a properly formatted Msg4 containing a NAS PDU (if necessary), allowing the NAS to determine whether it is communicating with a valid network.

[0015] NOTE: The current NAS specification does not mandate that the MME respond with anything to acknowledge receipt of the NAS PDU, so the NAS PDU is optional. Summary of the Invention [Problem to be solved by the invention]

[0016] The use of Early Data Transmission (EDT) via Msg3 (i.e., the current RRC Connection Request message, see Figures 1 and 2) requires specific Radio Access Network (RAN) functionality, such as a Physical Random Access Channel (PRACH) resource allocation for EDT broadcast in the System Information (SI). UEs 3 that are EDT-capable and intend to transmit small data via EDT use PRACH resources (e.g., PRACH preambles) specifically allocated in the Random Access Preamble message to access the network. UEs 3 select PRACH resources / preambles based on the resources broadcast in the SIB and the amount of data they intend to transmit. The PRACH resource / preamble selection can be based on random selection from the corresponding PRACH pool. In the case of a large number of UEs intending to use EDT, the PRACH resource allocation for EDT is broadcast, but the allocated PRACH resources / preambles may not be sufficient. This prevents some UEs from using the EDT functionality for data transfer, and these UEs instead use data transfer using control plane or user plane CIoT optimization.

[0017] The inventors have recognized that it would be advantageous to restrict the use of the EDT functionality (where and when necessary) to ensure that only certain subscribers (e.g., those authorized by subscription) can benefit from the EDT functionality.

[0018] Also, since mobile network operators may expose EDT as a service feature to service providers, it would be desirable to allow third-party service providers to query the EDT status and enable / disable the EDT feature on a per-UE basis.

[0019] Therefore, an object of the present disclosure is to provide a UE, a core network node, an access network node, a transmission control method, and a control method that solve the problem of difficulty in properly controlling EDT.

[0020] To achieve the above object, one aspect of the present disclosure provides a user equipment (UE) including a receiving means and a hardware processor, wherein the receiving means is configured to receive, from an access network node, a parameter indicating whether the user equipment is restricted or authorized to transmit user data in a message transmitted on an Uplink Synchronization Channel (UL-SCH), and the hardware processor is configured to process instructions for determining whether the transmission of the user data in the message is restricted or authorized based on the parameter.

[0021] Another aspect of the present disclosure provides a core network node including a memory and at least one processor, the memory for storing instructions, the processor configured to process the instructions to determine whether a user terminal is restricted or authorized to transmit user data in messages transmitted on an UL-SCH.

[0022] Also, an access network node according to another aspect of the present disclosure includes a transmitting means configured to transmit a parameter indicating whether a user terminal is restricted or authorized to transmit user data to the user terminal in a message transmitted on an UL-SCH and information of an authorized packet size for the transmission of the user data in the message.

[0023] Another aspect of the present disclosure is a method in a user terminal, which includes receiving, from an access network node, a parameter indicating whether the user terminal is restricted or authorized to transmit user data in a message transmitted on an UL-SCH, and processing instructions to determine whether the transmission of the user data in the message is restricted or authorized based on the parameter.

[0024] Another aspect of the present disclosure is a method in a core network node, which includes storing instructions and processing the instructions to determine whether a user terminal is restricted or authorized to transmit user data in messages transmitted on the UL-SCH.

[0025] Also, another aspect of the present disclosure is a method in an access network node, comprising transmitting a parameter indicating whether a user terminal is restricted or authorized to transmit user data to the user terminal in a message transmitted on an UL-SCH, and transmitting information of an authorized packet size for the transmission of the user data in the message.

[0026] Also, a system according to another aspect of the present disclosure includes a user terminal and an access network node, wherein the user terminal includes the configuration described in the above aspect of the present disclosure, and the access network node includes the configuration described in the above aspect of the present disclosure.

[0027] With the above-described configuration, the present disclosure can provide a UE, a core network node, an access network node, a transmission control method, and a control method that solves the problem of difficulty in appropriately controlling EDT. [Brief explanation of the drawings]

[0028] [Figure 1] FIG. 1 is a diagram illustrating an example of contention-based random access. [Figure 2] FIG. 2 is a diagram illustrating an example of a call flow for permitting data transmission. [Figure 3] Figure 3 shows EDT restriction / authorization control by the network during registration, attachment, or TAU / RAU procedures. [Figure 4] Figure 4 shows EDT restriction / authorization control by service operators via NEF / SCEF. [Figure 5] FIG. 5 illustrates paging of the EDT, where the use of the EDT is controlled. [Figure 6] FIG. 6 illustrates EDT congestion control in the RAN node 5. [Figure 7] Figure 7 illustrates the cases where EDT is prohibited for a cell, a group of cells, an entire registration area, or for the entire public land mobile network (PLMN). [Figure 8] FIG. 8 illustrates a schematic representation of a mobile (cellular or wireless) communication system 1. [Figure 9] FIG. 9 is a block diagram illustrating the main components of a UE. [Figure 10] FIG. 10 is a block diagram illustrating the main components of the RAN node 5. [Figure 11] FIG. 11 is a block diagram illustrating the main components of an exemplary core network node. DETAILED DESCRIPTION OF THE INVENTION

[0029] <First embodiment> Figures 3 to 7 schematically represent some example ways in which the above problems may be addressed. Figure 8 schematically represents a cellular communication system in which the techniques presented herein may be applied. Figures 9 to 11 are schematic block diagrams of some of the nodes shown in Figures 1 to 8.

[0030] Solution 1: EDT Restriction / Authorization by Network

[0031] Solution 1 proposes network-based EDT restriction / authorization control. EDT restriction / authorization control would enable the network (i.e., network operator) to restrict or authorize the use of EDT for each UE 3 or for a group of UEs. To restrict or authorize EDT for specific UEs, we propose introducing a new subscription parameter called the EDT restriction parameter (or EDT authorization parameter, or EDT prohibition parameter, or any other name for a parameter intended to authorize or restrict EDT use by a UE) in the unified data management (UDM) / unified data repository (UDR), home subscriber server (HSS), or home location register (HLR) 10. This parameter is maintained in the UDM / UDR, HSS, or HLR 10 and specifies whether the EDT function is restricted or authorized (permitted or not permitted) for a UE 3 per public land mobile network (PLMN). The EDT restriction / authorization parameter is configurable in the UDM / UDR, HSS, or HLR 10 via an operation and maintenance (O&M) module. Also, third party service providers can query or enable / disable EDT restriction / authorization parameters of the UDM / UDR, HSS or HLR 10 via the Network Exposure Function (NEF) or Service Function Exposure Function (SCEF) 13.

[0032] Figure 3 shows EDT restriction / authorization control by the network during registration, attachment, or TAU / RAU procedures.

[0033] 1a) If the UE3 is EDT capable and the UE3 supports the EDT restriction / authorization functionality (e.g., by subscribing to EDT restriction / authorization support), the UE3 indicates its ability to support EDT restriction / authorization (e.g., of the RAT (Radio Access Technology) that the UE3 is camped on) to the AMF / MME / SGSN9 in a suitably formatted Registration Request, Attach Request, or TAU / RAU Request message (and / or any other appropriate NAS message). In another aspect, the UE 3 may indicate its EDT feature support (e.g., an indicator that the UE 3 is EDT capable) in an appropriately formatted Registration Request, Attach Request, or TAU / RAU Request message (and / or any other appropriate NAS message), where the EDT feature support indicator is interpretable by the AMF, MME, or SGSN 9 to indicate that the UE 3 is EDT capable and that the UE 3 also supports EDT restriction / authorization procedures.

[0034] 1b) The UE 3 can optionally indicate support for EDT restriction / authorization to the AMF / MME / SGSN 9 indirectly via the RAN node 5 (e.g., base station, gNB, eNB, or RNC), i.e., first in an RRC message (e.g., a suitably formatted RRC Connection Request or RRC Connection Setup Complete or any other suitable AS message) to the RAN node 5 (gNB, eNB, or RNC), and the RAN node 5 then forwards the EDT restriction / authorization support parameters to the AMF / MME / SGSN 9 in an appropriate N2-AP / S1-AP UE Initial message, or any other suitable (existing or new) message, over the N2 / S1 interface between the RAN node 5 and the AMF / MME / SGSN 9. In another aspect, the UE 3 may indicate its EDT feature support (e.g., an indicator that the UE 3 is EDT capable) in the RRC Connection Request or RRC Connection Setup Complete or any other AS message, and consequently in the N2-AP / S1-AP UE Initial message, where the EDT feature support indicator can be interpreted by the AMF, MME or SGSN 9 to indicate that the UE 3 is EDT capable and that the UE 3 supports EDT restriction / authorization procedures as well.

[0035] 2) If the AMF / MME / SGSN 9 does not have subscription information for the UE 3, the AMF / MME / SGSN 9 may perform a UE subscription inquiry to the UDM / UDR, HSS or HLR 10 for the UE 3 (e.g., via an Update Location Request / Ack procedure or any other procedure for obtaining / inquiring UE subscription information from the UDM / UDR, HSS or HLR 10). This includes an EDT restriction / authorization subscription parameter for the UE 3. This parameter is kept as part of the subscription data in the UDM / UDR, HSS or HLR 10 and specifies whether EDT functionality is restricted for the UE 3. The EDT restriction / authorization can be per RAT within that PLMN, per PLMN, or for all PLMNs including the user's HPLMN.

[0036] 3) The AMF / MME / SGSN 9 updates the UE context with the latest status of the EDT restriction / authorization parameters received from the UDM / UDR, HSS or HLR 10.

[0037] 4) If the UE 3 is EDT capable and the UE indicated support for EDT restriction / authorization in step 1 via a NAS or AS message, the AMF / MME / SGSN 9 indicates to the RAN node 5 (gNB, eNB, or RNC) in the N2 / AP / S1-AP Initial Context Setup Request message (or any other message at the AMF / gNB, MME / eNB, or SGSN / RNC interface) whether the UE 3 is restricted or authorized to use EDT functionality in the RAN (based on the EDT restriction / authorization parameter value from the UDM / UDR, HSS, or HLR 10) whenever a UE context is established, e.g., during a service request procedure, a registration procedure, an attach procedure, and a TAU / RAU procedure. The AMF / MME / SGSN 9 also includes a Registration / Attach / TAU / RAU Accept message in the N2-AP / S1-AP Initial Context Setup Request message or a downlink NAS transport message to the RAN node 5. If the UE 3 included support for EDT restrictions / authorization in step 1, the AMF / MME / SGSN 9 includes the EDT restrictions / authorization parameters in the Registration Accept message / Attach Accept message / TAU Accept message / RAU Accept message or any other message to the UE 3. The EDT restriction / authorization parameter can take values ​​such as "restrict / do not restrict EDT", "prohibit / do not prohibit EDT", "authorize / do not authorize EDT", "use CIoT C-plane mechanism instead of EDT", "use CIoT U-plane mechanism instead of EDT", or "EDT is temporarily unavailable". If EDT is temporarily unavailable for some reason in the EPC or 5GC, for example, if the AMF / MME / SGSN 9 is congested or the NEF / SCEF 13 is congested, the AMF / MME / SGSN 9 may include an EDT back-off timer indicating the time during which the use of EDT is restricted. If the AMF / MME / SGSN 9 indicates "EDT is temporarily unavailable" to the UE 3 but does not indicate an EDT back-off timer, the UE 3 can use the back-off timer value of "CIoT C-plane back-off timer" if available in the registration accept message / attachment accept message / TAU accept message / RAU accept message, or any other NAS message.

[0038] 5) The RAN node 5 forwards the received NAS message (e.g., Registration / Attach / TAU / RAU Accept or any other NAS message) to the UE 3 in an RRC Connection Reconfiguration message or an RRC Direct Transfer message or any other appropriate RRC message.

[0039] 6) The UE3 is configured to use the value of the received EDT restriction / authorization parameter to determine whether the EDT feature is restricted or authorized (e.g., allowed or not, prohibited or not prohibited). If the UE 3 is EDT capable, the UE 3 assumes that EDT functionality is authorized unless explicitly restricted / prohibited by the network. If the EDT function is restricted / prohibited by the network, the UE 3 will not attempt EDT until the EDT restriction is explicitly lifted by the network (e.g., by signaling to the UE 3) or until the UE 3 moves to another RAT or PLMN. If the EDT feature is limited and an EDT back-off timer is included, the UE 3 will not attempt EDT until the EDT back-off timer expires.

[0040] Figure 4 shows EDT restriction / authorization control by service providers via NEF / SCEF13.

[0041] 1. The SCS / AS 12 (Service Capability Server / Application Server) sends an EDT request (including at least one of an external identifier or MSISDN, an SCS / AS identifier, and an EDT) message to the NEF / SCEF 13. The EDT parameter (or any other named parameter having the same purpose) indicates whether the request is to query the status of the EDT capability (e.g., restricted or not) of a specific UE or group of UEs in the UDM / UDR, HSS, or HLR 10, or to enable / disable EDT restriction / authorization subscription parameters.

[0042] 2. The NEF / SCEF 13 stores the SCS / AS identifier. The NEF / SCEF 13 assigns a NEF / SCEF Reference ID. If, based on operator policy, the SCS / AS 12 is not authorized to perform this request (e.g., the SLA does not allow it), or if the SCS / AS 12 has exceeded its quota or rate of EDT request transmissions, the NEF / SCEF 13 returns an EDT response (as shown in step 9) and provides a value for the EDT result parameter that appropriately indicates a failed result.

[0043] 3. The NEF / SCEF 13 sends an EDT request (EDT) message to the UDM / UDR, HSS or HLR 10.

[0044] 4. The UDM / UDR, HSS or HLR 10 checks the EDT request message, e.g., whether the EDT restriction / authorization functionality is supported by the serving AMF / MME / SGSN 9. If this check fails, the UDM / UDR, HSS or HLR 10 returns an EDT response message in step 8 and provides the NEF / SCEF 13 with a value for the EDT result parameter indicating failure. If the EDT request is to obtain the current status of the EDT restriction / authorization parameters of the UDM / UDR, HSS or HLR 10, the UDM / UDR, HSS or HLR 10 checks the value of the EDT restriction / authorization parameters and returns an EDT response message in step 8. In the EDT result parameter, the UDM / UDR, HSS or HLR 10 includes information about the EDT restriction, i.e., whether the use of the EDT feature is restricted or not (e.g., enabled or disabled). If the EDT parameter in the EDT request message is to enable or disable the EDT function, the UDM / UDR, HSS or HLR 10 sets the EDT restriction / authorization parameter of the UDM / UDR, HSS or HLR 10 to an appropriate value (e.g., whether EDT is allowed or not allowed).

[0045] 5. The UDM / UDR, HSS or HLR 10 sends an Insert Subscriber Data request to the AMF / MME / SGSN 9 to update the EDT restriction / authorization parameters in the AMF / MME / SGSN context (enable or disable the use of the EDT function).

[0046] 6. Based on operator policy, the AMF / MME / SGSN 9 may reject the request (e.g., overload or the UDM / UDR, HSS or HLR 10 has exceeded its quota or rate for sending EDT restriction / authorization requests). The AMF / MME / SGSN 9 updates the EDT restriction / authorization parameters in the AMF / MME / SGSN context. For example, the AMF / MME / SGSN 9 can be configured to transfer the EDT restriction / authorization parameters as part of its context information in the event of an AMF / MME / SGSN change. The AMF / MME / SGSN 9 updates the EDT restriction / authorization parameters of the UE in the next TAU / RAU, or the network may disconnect the UE indicating that reconnection is required based on local operator policy.

[0047] 7. If the EDT restrictions / authorizations are successfully updated, the AMF / MME / SGSN 9 sends an Insert Subscriber Data response message back to the UDM / UDR, HSS or HLR 10. The AMF / MME / SGSN 9 may include an EDT result parameter in the Insert Subscriber Data response message to indicate whether the update of the EDT restrictions / authorization parameters of the AMF / MME / SGSN context was successful or unsuccessful.

[0048] 8. The UDM / UDR, HSS or HLR 10 sends an EDT Response (NEF / SCEF Reference ID, EDT Result) message to the NEF / SCEF 13. The UDM / UDR, HSS or HLR 10 includes the EDT result indicating success / failure.

[0049] 9. The NEF / SCEF 13 sends an EDT Response (EDT Result) message to the SCS / AS 12. The EDT Result indicates success or failure. If in step 1 the EDT Request message was sent to query the status of the EDT restriction / authorization parameters of the UDM / UDR, HSS or HLR 10, the EDT Result parameter indicates the status of the EDT restriction / authorization parameters of the UDM / UDR, HSS or HLR 10, i.e., EDT is allowed or EDT is not allowed.

[0050] FIG. 5 illustrates EDT paging where EDT usage is restricted.

[0051] 1. The AMF / MME / SGSN 9 receives a Downlink Data Indicator (DDI) with a request for Early Data Transmission (EDT) in the downlink (EDT paging, or any other named indicator or parameter that means that the paging is for EDT in the downlink). The AMF / MME / SGSN 9 stores the received EDT paging indicator. If the EDT restriction / authorization parameter in the AMF / MME / SGSN context is not set to restrictive (e.g., the EDT restriction / authorization parameter is not set to restrictive), the AMF / MME / SGSN 9 includes the EDT paging parameter in each subsequent paging message to all gNBs / eNBs / RNCs 5 selected by the AMF / MME / SGSN 9 for paging.

[0052] 2. If the AMF / MME / SGSN 9 does not have information (EDT restriction / authorization parameter) about whether the paged UE 3 is authorized (i.e., not restricted) to use EDT, the AMF / MME / SGSN 9 performs a subscription query to the UDM / UDR, HSS or HLR 10 to obtain the UE's subscription information (e.g., by an Update Location Request / Ack procedure or any other procedure for obtaining / querying UE subscription information from the UDM / UDR, HSS or HLR 10).

[0053] 3. If the paged UE 3 is authorized for EDT (e.g., the EDT usage of this UE 3 is not restricted by subscription parameters such as EDT restrictions / authorizations), the AMF / MME / SGSN 9 decides to page the UE 3 for EDT.

[0054] 4. The AMF / MME / SGSN 9 sends a paging request to the connected RAN node 5, including the UE ID and the EDT paging parameters (or any other named parameters), indicating that the paging is for EDT.

[0055] 5. The RAN node 5 forwards the paging request in a system information broadcast message in which the paging message containing the EDT paging parameters is broadcast.

[0056] A mobile terminal that is EDT-capable and is being paged for EDT (i.e., the paging message includes EDT paging parameters) is configured to respond to the paging and pass data (e.g., data PDUs, NAS data) in Msg2 (RRC Connect / Disconnect Request message) according to the EDT data transmission procedure (e.g., using a PRACH preamble designed for EDT).

[0057] FIG. 6 illustrates EDT congestion control in a RAN node 5 (e.g., eNB / gNB).

[0058] 0. The RAN node 5 announces in the SIB that small user data transmission using the EDT mechanism is available in the RAN.

[0059] 1. UE3 sends a properly formatted Msg1, e.g., a random access preamble.

[0060] 2. If PRACH resources are scarce at the RAN, the RAN sends a properly formatted Msg2 to the UE 3 with the RAR uplink grant and the "Allowed Packet Size for EDT".

[0061] 3. If the "Allowed Packet Size for EDT" in Msg2 (Random Access Response message) is specified in the RAN, UE3 compares the "Allowed Packet Size for EDT" received from the RAN with the user data sent from upper layers of UE3 to determine whether UE3 can send user data in Msg3 (e.g., RRC Connection Request or EDT Data Request or any other named message for EDT purposes). If UE3's user data is larger than the "Allowed Packet Size for EDT", UE3 falls back to the normal CIoT Mobile Originated (MO) procedure using an appropriately formatted Msg5 (e.g., RRC Connection Setup Complete) or using data transmission over the user plane.

[0062] In summary, Figure 6 shows the use case where UE3 sends Msg3 with EDT data because the size of the user data to be transmitted is smaller than the "authorized packet size for EDT" in the random access response of Msg2.

[0063] Figure 7 shows the case where EDT is prohibited in a cell, a group of cells, an entire registration area or an entire PLMN: it is possible for a network operator to request that EDT be prohibited for all UEs in a cell, a group of cells or a registration area.

[0064] 1) Based on operator policy or configuration in the AMF / MME / SGSN 9 or O&M module, the AMF / MME / SGSN 9 can indicate an EDT prohibition indicator / parameter to the RAN node 5 in a properly formatted AMF / MME configuration command, or an N2-AP or S1-AP initial configuration request message, or any other appropriate (new or existing) message on the N2 / S1 interface between the AMF / MME / SGSN 9 and the RAN node 5 (e.g., gNB or eNB or RNC). The EDT prohibition indicator / parameter (or any other named indicator / parameter for whether to prohibit EDT) can take values ​​such as "EDT prohibited", "EDT not prohibited", or any other value for controlling the restriction or authorization of EDT use by UEs. The AMF / MME / SGSN 9 can indicate the EDT prohibition indicator to one RAN node, a group of RAN nodes, or all RAN nodes within a registration area. If the included EDT prohibition indicator is set to ON (i.e., EDT is prohibited), the AMF / MME / SGSN 9 may also include in the same N2 / S1 message an EDT back-off timer that defines the time for which EDT is prohibited.

[0065] 2) When the RAN node 5 receives an EDT prohibition indicator in an N2 / S1 message from the AMF / MME / SGSN 9 (e.g., an AMF / MME configuration command message, an N2-AP / S1-AP initial configuration request message or any other message from the AMF / MME / SGSN 9), the RAN node 5 stores the received EDT prohibition indicator and sets the EDT prohibition indicator in the SI broadcast to reflect the EDT prohibition indicator from the AMF / MME / SGSN 9. If an EDT back-off timer is included, the RAN node 5 will continue to broadcast the EDT forbidden status until the EDT back-off timer expires or until it receives a new EDT indicator from the AMF / MME / SGSN 9 that resets the forbidden status (e.g. allows the UE to use EDT). If the EDT back-off timer is not included, the RAN node 5 will continue to broadcast the EDT forbidden status until it receives a new EDT indicator from the AMF / MME / SGSN 9 that resets the forbidden status (e.g. allows the UE to use EDT).

[0066] 3) When UE3 in idle mode reads system information: If the EDT indicator / parameter in the system information (SI) indicates that EDT is prohibited, the UE 3 must not begin transmitting data using EDT until the EDT indicator in the SI indicates the prohibited status. If the EDT indicator / parameter in the system information (SI) indicates that EDT is not prohibited, or if the EDT status indicator is not present at all, the UE 3 may initiate data exchange using EDT, unless EDT is restricted by any other means.

[0067] Note: All the above 3G / 4G solution suggestions are equally applicable to 5G where AMF, NEF instead of SCEF, UDM / UDR instead of HSS / HLR are used instead of MME / SGSN. RAN nodes may include RNC in 3G, eNB in ​​4G, and gNB or NG-RAN in 5G.

[0068] overview

[0069] Beneficially, the above exemplary aspects include, but are not limited to, one or more of the following features.

[0070] 1) A new subscription parameter in the UDM / UDR, HSS or HLR called the EDT restriction parameter (or EDT authorization parameter, or any other name for the parameter intended to authorize or restrict the use of EDT by the UE).

[0071] 2) The UE indicates support for EDT or support for EDT restrictions or authorizations to the AMF / MME / SGSN in an appropriately formatted NAS message (e.g., Register, Attach, TAU / RAU request message).

[0072] 3) The AMF / MME / SGSN updates the UE context with the latest status of the EDT restriction / authorization parameters when querying the UDM / UDR, HSS, or HLR for UE subscription information.

[0073] 4) If the UE includes support for EDT restriction / authorization in the registration / attachment / TAU / RAU request, the AMF / MME / SGSN provides the EDT restriction / authorization parameters to the UE in a registration / attachment / TAU / RAU acceptance message or any other NAS message.

[0074] 5) EDT restriction / authorization control by service operators via NEF / SCEF.

[0075] 6) Paging for EDT if the UE is EDT capable and the UE is not restricted by subscription from using EDT.

[0076] 7) The EDT resource grant in the random access response message and the UE's use of EDT is data for transmission below the granted resources for EDT.

[0077] 8) EDT prohibition in a cell, group of cells, registration area or entire PLMN via EDT prohibition indicator / parameter broadcast in system information.

[0078] It will be appreciated that the above aspects describe methods that include one or more of the following steps:

[0079] 1) A new subscription parameter definition for UDM / UDR, HSS or HLR called EDT restriction parameter (or EDT authorization parameter, or any other name for the parameter intended to authorize or restrict EDT use by the UE).

[0080] 2) The UE indicates support for EDT or support for EDT restrictions or authorizations to the AMF / MME / SGSN in a NAS message (e.g., registration, attach, TAU / RAU request message).

[0081] 3) Alternatively, the UE first indicates support for EDT or support for EDT restrictions or authorization to the RAN node (gNB, eNB, or RNC) in an RRC message (e.g., RRC Connection Request or RRC Connection Setup Complete or any other AS message), and then the RAN node forwards the EDT restriction / authorization support parameters to the AMF / MME / SGSN in an N2-AP / S1-AP UE Initial message or any other existing or new message on the N2 / S1 interface between the RAN node and the AMF / MME / SGSN.

[0082] 4) The AMF / MME / SGSN updates the UE context with the latest status of EDT restriction / authorization parameters when querying the UDM / UDR, HSS or HLR for UE subscriber information.

[0083] 5) If the UE includes support for EDT restriction / authorization in the registration / attachment / TAU / RAU request, the AMF / MME / SGSN provides the EDT restriction / authorization parameters to the UE in a registration accept message / attachment accept message / TAU accept message / RAU accept message or any other NAS message.

[0084] 6) EDT restriction / authorization control by service operators via NEF / SCEF.

[0085] 7) Paging for EDT if the UE is EDT capable and the UE is not restricted by subscription from using EDT.

[0086] 8) The EDT resource grant in the random access response message and the UE's use of the EDT is data for transmission below the granted resources for the EDT.

[0087] 9) EDT prohibition in a cell, group of cells, registration area or entire PLMN using EDT prohibition indicator / parameter broadcast in system information.

[0088] It will be appreciated that the above embodiments advantageously provide many advantages, including (but not limited to) those mentioned above.

[0089] The proposed EDT restriction / authorization control allows the network (i.e., network operator) to restrict or authorize the use of EDT per UE or group of UEs. To restrict or authorize EDT for specific UEs, a new subscription parameter in the UDM / UDR, HSS, or HLR, called the EDT restriction parameter, is proposed to be introduced. In this way, network operators can prioritize EDT usage in locations and times where not all EDT-capable UEs can utilize the EDT feature.

[0090] System appearance

[0091] FIG. 8 illustrates schematically a mobile (cellular or wireless) communication system 1 to which the above-described aspects can be applied.

[0092] In this network, users of mobile devices 3A-3C (or User Equipment "UE") can communicate with each other or other users via respective base stations 5 and a core network 7 using 5G radio access technology (RAT). It will be appreciated that multiple base stations 5 (or "gNBs" in 5G networks, "eNBs" in LTE) form a (radio) access network. As will be appreciated by those skilled in the art, while FIG. 8 shows three mobile devices 3 and one base station 5 for illustrative purposes, a system when implemented will typically include other base stations and mobile devices. It will also be appreciated that the (radio) access network may support E-UTRA radio access technology (e.g., instead of or in addition to 5G).

[0093] Typically, the core network 7 includes logical nodes (or "functions") for supporting communications in the communications system 1. Typically, for example, the core network 7 in a "next generation" / 5G system includes, among other functions, control plane functions and user plane functions.

[0094] As is known, a mobile device 3 may move around within a geographic area covered by the communication system 1, entering and leaving areas (i.e., radio cells) served by base stations 5 or (R)ANs. To keep track of the mobile device 3 and facilitate its movement between different base stations 5, the core network 7 includes at least one Access Mobility Management Function (AMF) 9. The AMF 9 is in communication with the base stations 5 connected to the core network 7. Depending on the core network, the functions of the AMF 9 may be performed by a Mobility Management Entity (MME) or a Serving GPRS Support Node (SGSN).

[0095] The core network 7 also includes a UDM / UDR 10 (and / or an HSS / HLR, as appropriate), one or more gateways 11, one or more application functions (AFs) 12, etc. Although not shown in Figure 8, the core network 7 may include further nodes such as a network publishing function (NEF), a service function publishing function (SCEF), etc.

[0096] The mobile device 3 and each serving base station 5 are connected via an appropriate air interface (such as the so-called "Uu" interface). Adjacent base stations 5 are connected to each other via appropriate inter-base station interfaces (such as the so-called "X2" interface, "Xn" interface, etc.), either directly or by an appropriate (home) base station gateway. Each base station 5 is also connected to core network nodes 9 / 10 / 11 / 12 / 13 via appropriate interfaces (such as the so-called "S1", "N2" / "N3" interfaces, etc.). From the core network 7, connectivity to external IP networks 20 (such as the Internet) is also provided.

[0097] User Equipment (UE)

[0098] FIG. 9 is a block diagram illustrating the main components of a mobile device 3 (UE 3). As shown, the UE 3 includes a transceiver circuit 31 operable to transmit and receive signals to and from connected nodes via one or more antennas 32. While not necessarily shown in FIG. 9, the UE 3 naturally includes all of the typical functionality of a conventional mobile device (e.g., a user interface 35), which may be provided by any one or any combination of hardware, software, and firmware, as appropriate. The software may be pre-installed in memory 34 and / or downloaded via a communications network or from a removable data storage device (RMD). The controller 33 controls the operation of the UE 3 in accordance with software stored in memory 34. The software includes, among other things, an operating system 341 and a communications control module 342 having at least a transceiver control module 3421. The communication control module 342 (using its transceiver control module 3421) is responsible for handling (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes such as the base station 5 and the core network nodes 9 / 10 / 11 / 12 / 13. Such signaling may include, for example, appropriately formatted signaling messages related to EDT restriction / admission control (for the UE 3) (e.g. registration requests and related responses), in particular registration request, attachment request, or TAU / RAU request messages (any other NAS messages), and / or signaling messages related to random access procedures.

[0099] RAN node

[0100] FIG. 10 is a block diagram illustrating the main components of a RAN node 5 (RNC or base station, e.g., eNB / gNB). As shown, the RAN node 5 includes a transceiver circuit 51 operable to transmit and receive signals to and from a UE 3 via one or more antennas 52, and to transmit and receive signals to and from core network nodes 9 / 10 / 11 / 12 / 13 via a network interface 55 (e.g., S1 / N2 / N3). The transceiver circuit 51 may also be operable to transmit and receive signals to and from other base stations via the network interface 55 (e.g., via an X2 or Xn interface). A controller 53 controls the operation of the RAN node 5 according to software stored in a memory 54. The software may, for example, be pre-installed in the memory 54 and / or downloaded via a communication network or from a removable data storage device (RMD). The software includes, among other things, an operating system 541 and a communication control module 542 having at least a transceiver control module 5421. The communications control module 542 (using its transceiver control module 5421) is responsible for handling (generating / sending / receiving) signaling between the RAN node 5 and other nodes such as the UE 3 and the core network nodes 9 / 10 / 11 / 12 / 13 (and other RAN nodes / base stations 5 as appropriate). Such signaling may include, for example, appropriately formatted signaling messages related to EDT restriction / admission control.

[0101] Core Network Node

[0102] 11 is a block diagram depicting the major components of an exemplary core network node 9 / 10 / 11 / 12 / 13. As shown, the core network node 9 / 10 / 11 / 12 / 13 includes transceiver circuitry 91 / 101 / 111 / 121 / 131 operable to transmit and receive signals to and from other network nodes (directly or indirectly) via a network interface 94 / 104 / 114 / 124 / 134. A controller 92 / 102 / 112 / 122 / 132 controls the operation of the core network node 9 / 10 / 11 / 12 / 13 in accordance with software stored in memory 93 / 103 / 113 / 123 / 133. The software may be pre-installed in the memory 93 / 103 / 113 / 123 / 133 and / or may be downloaded, for example, via a communications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 931 / 1031 / 1131 / 1231 / 1331 and a communications control module 932 / 1032 / 1132 / 1232 / 1332 having at least a transceiver control module 9321 / 10321 / 11321 / 12321 / 13321. The communications control module 932 / 1032 / 1132 / 1232 / 1332 (using its own transceiver control module 9321 / 10321 / 11321 / 12321 / 13321) is responsible (directly or indirectly) for handling (generating / sending / receiving) signaling between the core network node 9 / 10 / 11 / 12 / 13 and other nodes, such as the UE 3, other core network nodes 9 / 10 / 11 / 12 / 13 and the RAN node 5. The signaling may include, for example, appropriately formatted signaling messages related to EDT restriction / admission control. If the core network node 9 / 10 / 11 / 12 / 13 provides UDM / UDR, HSS or HLR functionality, it is configured to store new subscription parameters, referred to herein as EDT restriction parameters (or EDT authorization parameters, or EDT prohibition parameters, or any other name for parameters intended to authorize or restrict EDT for use by the UE).

[0103] Variations and alternatives

[0104] Detailed embodiments have been described above. As will be appreciated by those skilled in the art, numerous modifications and alternatives can be made to the above embodiments while still benefiting from the disclosure embodied herein. For purposes of illustration, only a few of these alternatives and modifications will now be described.

[0105] In the above description, for ease of understanding, the UE, RAN node, and core network node are described as having several separate modules (e.g., communication control modules). These modules may be provided in this manner for specific applications, such as when an existing system is modified to implement the present disclosure, or for other applications, such as when a system is designed from the beginning with the inventive features in mind; however, these modules may not be recognized as separate entities because they are incorporated into the overall operating system or code. These modules may also be implemented in software, hardware, firmware, or a combination thereof.

[0106] Each controller may include any suitable type of processing circuitry, including, but not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control, data, and / or address buses), direct memory access (DMA) functions, hardware or software-implemented counters, pointers, and / or timers, etc.

[0107] The above embodiments describe several software modules. As will be appreciated by those skilled in the art, the software modules may be provided in compiled or uncompiled form, or may be supplied to the UE, RAN node, and core network node as signals, via a computer network, or on a recording medium. Furthermore, the functions performed by some or all of this software may be performed using one or more dedicated hardware circuits. The use of software modules is preferred because it facilitates updating the UE, RAN node, and core network node to update their functions.

[0108] In the above embodiments, 3GPP wireless communication (radio access) technologies are used, however, other wireless communication technologies (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) can also be used in accordance with the above embodiments.

[0109] The term user terminal includes, for example, communication devices such as mobile phones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, etc. Such mobile (or even normally stationary) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices may also be connected to the network. For simplicity, this application refers to mobile devices (or UE) in the specification, but it will be understood that the described techniques may be implemented for any communication device (mobile and / or normally stationary) capable of connecting to a communication network for the transmission and reception of data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

[0110] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0111] Abbreviations and Terms The following abbreviations and terms are used herein: 3GPP 3rd Generation Partnership Project 5G-AN 5G Access Network 5G-RAN 5G Radio Access Network 5GS 5G System 5G System AF Application Function AMF Access and Mobility Management Function AS Access Stratum AUSF Authentication and Security Function Authentication and security function CIoT Cellular Internet of Things CP Control Plane DL Down Link DNN Data Network Name Data network name EDT Early Data Transmission EPS Evolved Packet System Improved packet system HARQ Hybrid Automatic Repeat Request Hybrid automatic repeat request HLR Home Location Register HSS Home Subscriber Server Home Subscriber Server eMTC enhanced Machine Type Communication eNB enhanced NodeB Improved NodeB gNB Next Generation NodeB Next Generation NodeB MAC Medium Access Control ME Mobile Equipment MME Mobility management entity NB-IoT Narrow Band Internet of Things NAS Non Access Stratum NF Network Function NEF Network Exposure Function NR New Radio New Radio O&M Operation and Maintenance PCF Policy Control Function SCEF Service Capability Exposure Function SGSN Serving GPRS Support Node PRACH Physical Random Access Channel Physical Random Access Channel (R)AN Radio Access Network RAR Random Access Response RAU Routing Area Update RNC Radio Network Controller RRC Radio Resource Control SIB System Information Module SIM Subscriber Interface Module TAU Tracking Area Update Tracking Area Update UDM Unified Data Management UDR Unified Data Repository UE User Equipment User terminal UL Up Link

[0112] Additional notes (Appendix 1) A user terminal, means for receiving from an access network node a parameter indicating whether the user terminal is restricted or authorized to transmit user data in a message transmitted on an Uplink Synchronization Channel (UL-SCH); means for determining whether the transmission of the user data in the message is restricted or authorized based on the parameters; A user terminal comprising: (Appendix 2) means for transmitting information of the transmission capability of the user data in the message to a core network node via the access network node; 2. The user terminal of claim 1, wherein the receiving means further receives the parameters after transmitting the information of the capability of the transmission of the user data in the message. (Appendix 3) means for transmitting capability information supporting restricting or authorizing the transmission of the user data in the message to a core network node via the access network node; 2. The user terminal of claim 1, wherein the receiving means further receives the parameters based on the information of the capability to support restricting or authorizing the transmission of the user data in the message. (Appendix 4) 4. The user terminal of claim 3, wherein the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message is based on a user terminal context updated by the core network node. (Appendix 5) 4. A user terminal as described in any one of Supplementary Notes 1 to 3, wherein the parameter indicating whether the user terminal is restricted or authorized to send the user data in the message is indicated each time a user terminal context is established. (Appendix 6) the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message is broadcast from the access network node; the receiving means further receives information of an allowed packet size for the transmission of the user data in the message; The user terminal of claim 1, wherein the determining means further determines whether the user terminal transmits the user data based on the information of the allowed packet size for the transmission of the user data in the message. (Appendix 7) the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message is broadcast from the access network node; 2. The user terminal of claim 1, wherein the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message indicates that the transmission is prohibited. (Appendix 8) the receiving means further receives the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message and a value of a back-off timer for the transmission of the user data; 8. The user terminal of claim 1, wherein the determining means further determines whether the user terminal transmits the user data in the message based on the value of the back-off timer. (Appendix 9) 9. The user terminal of claim 8, further comprising: means for not attempting to transmit the user data in the message until the user terminal moves to another Radio Access Technology (RAT) or until the restriction on the transmission of the user data in the message is lifted by the core network node. (Appendix 10) The receiving means further receives a value "Early Data Transmission (EDT) temporarily unavailable" from the core network node; 8. The user terminal of claim 1, further comprising: means for not attempting to transmit the user data in the message until a back-off timer for a Cellular Internet of Things (CIoT) control plane of the user terminal expires. (Appendix 11) A core network node, A core network node comprising means for determining whether a user terminal is restricted or authorized to transmit user data in messages transmitted on an Uplink Synchronization Channel (UL-SCH). (Appendix 12) 12. The core network node of claim 11, further comprising means for transmitting to the user terminal via an access network node a parameter indicating whether the user terminal is restricted or authorized for the transmission of the user data in the message. (Appendix 13) means for receiving information of the capability of the transmission of the user data in the message from the user terminal via the access network node; 13. The core network node of claim 12, wherein the means for transmitting further transmits the parameters based on the information of the capability of the transmission of the user data in the message. (Appendix 14) means for receiving from the user terminal via the access network node capability information supporting restricting or authorizing the transmission of the user data in the message; 13. The core network node of claim 12, wherein the means for transmitting further transmits the parameters based on the information of the capability to support restricting or authorizing the transmission of the user data in the message. (Appendix 15) The transmitting means further transmits a request for subscription information corresponding to the user terminal to a subscription data server; the receiving means further receives the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message. 15. The core network node according to claim 14. (Appendix 16) The receiving means further receives an Insert Subscriber Data Request from a subscription data server; the core network node further comprising means for updating the parameter indicating whether the user terminal is restricted or authorized for the transmission of the user data in the message; 16. The core network node according to any one of Supplementary Notes 12 to 15, wherein the transmitting means is further configured to transmit the updated parameters to the user equipment. (Appendix 17) means for receiving a Downlink Data Indication (DDI) from a user plane data network node together with a request for the transmission of the user data in the message; means for transmitting a paging request to the user terminal for the transmission of the user data in the message based on a result of determining whether the user terminal is restricted or authorized for the transmission of the user data in the message; 12. The core network node of claim 11, further comprising: (Appendix 18) the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message indicates that the transmission is prohibited; The transmitting means further transmits a configuration command to the access network node, the configuration command including the parameter indicating that the transmission is prohibited; the access network node is further configured to broadcast the parameter indicating that the transmission is prohibited to at least the user terminal. 17. A core network node according to any one of Supplementary Notes 12 to 16. (Appendix 19) an access network node, a parameter indicating whether the user terminal is restricted or authorized to transmit user data to the user terminal in messages transmitted on the Uplink Synchronization Channel (UL-SCH); information about an allowed packet size for the transmission of the user data in the message; and an access network node comprising means for transmitting (Appendix 20) 1. A method in a user terminal, comprising: receiving from an access network node a parameter indicating whether the user terminal is restricted or authorized to transmit user data in a message transmitted on an Uplink Synchronization Channel (UL-SCH); processing instructions to determine whether the transmission of the user data in the message is restricted or authorized based on the parameters; The method includes: (Appendix 21) Sending information of the transmission capability of the user data in the message to a core network node via the access network node; receiving the parameters after transmitting the information of the capability of the transmission of the user data in the message; 21. The method of claim 20, further comprising: (Appendix 22) transmitting capability information supporting restricting or authorizing the transmission of the user data in the message to a core network node via the access network node; receiving the parameters based on the information of the capabilities that support restricting or authorizing the transmission of the user data in the message; 21. The method of claim 20, further comprising: (Appendix 23) 23. The method of claim 22, wherein the parameter indicating whether the user terminal is restricted or authorized for the transmission of the user data in the message is based on a user terminal context updated by the core network node. (Appendix 24) 24. The method of any one of Supplementary Notes 20 to 23, wherein the parameter indicating whether the user terminal is restricted or authorized to send the user data in the message is indicated each time a user terminal context is established. (Appendix 25) the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message is broadcast from the access network node; The method comprises: receiving information about an allowed packet size for the transmission of the user data in the message; determining whether to transmit the user data based on the information of the allowed packet size for the transmission of the user data in the message; 21. The method of claim 20, further comprising: (Appendix 26) the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message is broadcast from the access network node; 21. The method of claim 20, wherein the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message indicates that the transmission is prohibited. (Appendix 27) receiving the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message and a back-off timer value for the transmission of the user data; processing instructions for the user terminal to determine whether to transmit the user data in the message based on the value of the back-off timer; 27. The method of any one of claims 20 to 26, further comprising: (Appendix 28) 28. The method of claim 27, further comprising not attempting to transmit the user data in the message until the user terminal moves to another Radio Access Technology (RAT) or until the restriction on the transmission of the user data in the message is lifted by the core network node. (Appendix 29) receiving a value "Early Data Transmission (EDT) temporarily unavailable" from the core network node; not attempting the transmission of the user data in the message until a back-off timer for a Cellular Internet of Things (CIoT) control plane of the user terminal expires; 27. The method of any one of claims 20 to 26, further comprising: (Appendix 30) 1. A method in a core network node, comprising: Memorize the command, processing instructions to determine whether the user terminal is restricted or authorized to transmit user data in messages transmitted on an Uplink Synchronization Channel (UL-SCH); The method includes: (Appendix 31) 31. The method of claim 30, further comprising transmitting to the user terminal via an access network node a parameter indicating whether the user terminal is restricted or authorized for the transmission of the user data in the message. (Appendix 32) receiving information of the capability of the transmission of the user data in the message from the user terminal via the access network node; transmitting the parameters based on the information of the capability of the transmission of the user data in the message. 32. The method of claim 31, further comprising: (Appendix 33) receiving from the user terminal via the access network node capability information that supports restricting or authorizing the transmission of the user data in the message; transmitting the parameters based on the information of the capabilities that support restricting or authorizing the transmission of the user data in the message. 32. The method of claim 31, further comprising: (Appendix 34) Sending a request for subscription information corresponding to the user terminal to a subscription data server; receiving the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message; 34. The method of claim 33, further comprising: (Appendix 35) Receives an Insert Subscriber Data Request from the subscription data server; processing instructions to update the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message; transmitting the updated parameters to the user terminal; 35. The method of any one of claims 31 to 34, further comprising: (Appendix 36) receiving a Downlink Data Indication (DDI) from a network node for user plane data with a request for the transmission of the user data in the message; transmitting a paging request to the user terminal for the transmission of the user data in the message based on a result of determining whether the user terminal is restricted or authorized for the transmission of the user data in the message; 31. The method of claim 30, further comprising: (Appendix 37) the parameter indicating whether the user terminal is restricted or authorized to transmit the user data in the message indicates that the transmission is prohibited; The method comprises: sending a configuration command to the access network node including the parameter indicating that the transmission is prohibited; broadcasting the parameter indicating that the transmission is prohibited to at least the user terminal; 36. The method of any one of claims 31 to 35, further comprising: (Appendix 38) 1. A method in an access network node, comprising: transmitting a parameter indicating whether the user terminal is restricted or authorized to transmit user data to the user terminal in a message transmitted on an Uplink Synchronization Channel (UL-SCH); transmitting information about an allowed packet size for the transmission of the user data in the message; The method includes: (Appendix 39) 1. A system comprising: A user terminal according to any one of Supplementary Notes 1 to 10; an access network node according to Supplementary Note 19; and A system comprising:

[0113] This application claims the benefit of priority from European Patent Application No. 17202452.3, filed November 17, 2017, the entire contents of which are incorporated herein by reference. [Explanation of symbols]

[0114] 1. Communication Systems 3UE 31 Transceiver Circuit 32 Antenna 33 Controller 34 memory 341 Operating Systems 342 Communication Control Module 3421 Transceiver Control Module 35 User Interface 5 eNB, RAN node 51 Transceiver circuit 52 Antenna 53 Controller 54 memory 541 Operating Systems 542 Communication Control Module 5421 Transceiver Control Module 55 Network Interface 7 Core Network 9 AMF / MME / SGSN 10 UDM / UDR or HSS / HLR 11 SGW / PGW(GW) 12 SCS / AS 13 NEF / SCEF 91 / 101 / 111 / 121 / 131 Transceiver circuit 92 / 102 / 112 / 122 / 132 controller 93 / 103 / 113 / 123 / 133 memory 931 / 1031 / 1131 / 1231 / 1331 Operating Systems 932 / 1032 / 1132 / 1232 / 1332 communication control module 9321 / 10321 / 11321 / 12321 / 13321 Transceiver Control Module 94 / 104 / 114 / 124 / 134 network interfaces 20 External IP Network

Claims

1. Sending a Non-Access-Stratum (NAS) message including first information to a core network device, the first information comprising a control unit indicating that the terminal device supports a first function; the control unit receives a paging message including parameters related to the first function from a base station device that has received a paging message from the core network device; the first function is an early data transmission function; Terminal device.

2. The NAS message includes a tracking area update message. The terminal device according to claim 1 .

3. The first information indicates that the terminal device supports the first function for a control plane. The terminal device according to claim 1 .

4. The first information indicates that the terminal device supports the first function for a user plane. The terminal device according to claim 1 .

5. The control unit receives, from the base station device, a radio resource control message including downlink data transmitted from the core network device to the base station device. The terminal device according to claim 1 .

6. sending a Non-Access-Stratum (NAS) message to a core network device, the NAS message including first information, the first information indicating that the terminal device supports a first function; receiving a paging message including parameters related to the first function from a base station device that has received the paging message from the core network device; the first function is an early data transmission function; Terminal device method.

Images