Early Data Sending Authorization Control

Abstract

The present invention provides a user equipment, i.e., UE, comprising: a receiver configured to receive a parameter from an access network node for indicating whether the UE is restricted or authorized to send user data in a message sent on an uplink synchronization channel, i.e., UL-SCH; and a hardware processor configured to process instructions to determine whether the UE is restricted or authorized to send user data in a message based on the parameter.

Description

Technical Field

[0001] The present invention relates to communication systems. In particular, but not exclusively, the present invention relates to wireless communication systems and apparatus thereof operating in accordance with the Third Generation Partnership Project (3GPP) standards or their equivalents or derivatives. In particular, but not exclusively, the present invention relates to authorization control of Early Data Transmission (EDT) in so-called "next generation" systems. Background Art

[0002] 3GPP working groups are discussing how to introduce the EDT feature for Re1-15 enhanced machine type communications (eMTC) and narrowband Internet of Things (NB-IoT). This feature allows user equipment (UE) (using control plane and user plane cellular IoT (CIoT) evolved packet system (EPS) optimization) to send small data in the radio resource control (RRC) message 3 (Msg3: a message sent in the uplink synchronization channel (UL-SCH) containing the cell radio network temporary identifier (C-RNTI), medium access control control element (MAC CE) or common control channel service data unit (CCCH SDU) submitted from upper layers as part of the random access procedure and associated with the UE contention resolution identifier). Note that MsgX in the following text generally refers to step X in the contention-based random access procedure, see Figure 1 (TS 36.300, Fig.10 .1.5.1-1). For example, the message represented by "Msg3" is the first scheduled uplink (UL) message based on the grant provided by the random access response (RAR) message. Normal downlink (DL) / UL transmission can be performed after the random access procedure.

[0003] To date, 3GPP RAN2 working group protocols are communicated using LS R2-1711978 / S2-177180.

[0004] [Table 1]

[0005]

[0006] 3GPP RAN2 further discussed the details of the EDT feature and made the following agreement in RAN2#99bis.

[0007] [Table 2]

[0008]

[0009] As mentioned above, RAN2 intends to support early UL data transmission in Msg3 for control plane and user plane CIoT Evolved Packet System (EPS) optimization.

[0010] According to the current procedure, the transmission of Msg3 is based on the initial UL grant provided by the RAR, which makes the size of the transport block dependent on the grant. In the case where uplink transmission is required (e.g., for contention resolution), the evolved NodeB (eNB) should not provide a grant smaller than 56 bits (or 88 bits for NB-IoT) in the RAR (see TS 36.300).

[0011] Msg3 and Msg4 (contention resolution) (see Figure 1 ) uses Hybrid Automatic Repeat Request (HARQ) processing. According to the current specification, Msg3 carries at least a 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 a higher priority than the UL buffer).

[0012] Control Plane (CP) CIoT EPS optimizes early data transmission

[0013] Figure 2 An exemplary call flow that allows data to be sent in Msg3(UL) and / or Msg4(DL) as NAS protocol data units (PDUs) is shown in FIG. The steps are briefly described below.

[0014] A. Resource determination: The eNB 5 decides to allow early transmission of small data packet sizes without establishing a full RRC connection. The eNB 5 allocates Physical Random Access Channel (PRACH) resources for this purpose.

[0015] 0. The eNB 5 announces resources via System Information Broadcast (SIB).

[0016] B. The UE 3 selects a PRACH resource based on the announced resources and the amount of data to be sent. The selection may be based on a random selection from the corresponding PRACH pool.

[0017] Note: If no PRACH resources are broadcast in Msg0 for data in Msg3 procedure, or UE 3 intends to perform NAS signaling procedure or UE 3 intends to send / receive more possible data in one medium access control (MAC) block, UE 3 uses the conventional RRC connection establishment / recovery procedure.

[0018] 1. UE 3 sends a properly formatted PRACH preamble (Msg1: Random Access Preamble).

[0019] 2. UE 3 receives RAR (Msg2). In current Long Term Evolution (LTE), RAR may contain uplink grant and timing advance (TA) (in addition to temporary C-RNTI, etc.). In order to enable data transmission in Msg3, RAR may be updated to include power control information. Otherwise, UE 3 may use open loop power control (i.e., UE 3 determines the transmit power by itself).

[0020] 3. UE 3 sends a suitably formatted Msg3 with a UE identifier (UEID) (discussed later) and a NAS PDU using the UL grant indicated in the RAR. UE 3 takes into account the power control information from the RAR if included. UE 3 starts the contention resolution timer after this step.

[0021] 4-6. The eNB 5 selects the appropriate mobile management entity (MME) 9 based on the UEID 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 is available for the UE 3, the serving gateway (SGW) 11 provides the downlink data to the MME 9, the MME 9 forwards the downlink data as a NAS PDU to the eNB 5, and the NAS PDU is delivered to the UE 3. If the eNB 5 has indicated that the UE 3 has initiated early data transmission, in response, the MME 9 may also be configured to close the relevant S1-AP connection after forwarding any downlink NAS PDU. The MME 9 may also use this indication to prioritize UL data and speed up step 6.

[0022] 7. The network responds with a suitably formatted Msg4 (thereby acknowledging receipt of Msg3), completing contention resolution, and including a NAS PDU (if required). If a NAS PDU is included, the NAS will be able to confirm that it is communicating with a valid network.

[0023] NOTE: The current NAS specification does not require any response from the MME to acknowledge receipt of a NAS PDU, so the NAS PDU is optional. Summary of the invention

[0024] Problem that the invention aims to solve

[0025] In Msg3 (i.e., the current RRC connection request message, see Figure 1 and Figure 2) will require specific radio access network (RAN) functions, such as the physical random access channel (PRACH) resource allocation for EDT, which will be broadcast in the system information (SI). UE 3 that is capable of EDT and wants to send small data via EDT will use the specially allocated PRACH resources (e.g., PRACH preamble) in the random access preamble message to access the network. UE 3 selects PRACH resources / preamble based on the announced resources in the SIB and the amount of data that UE 3 wants to send. The selection of PRACH resources / preamble can be based on a random selection from the corresponding PRACH pool. Although the PRACH resource allocation for EDT is broadcast, if there are many UEs that want to use EDT, the allocated PRACH resources / preamble may not be enough. This will result in some UEs being unable to use the EDT feature for data transmission, and instead, these UEs will use data transmission via control plane or user plane CIoT optimization.

[0026] The inventors have recognised that it would be advantageous to restrict (where and where necessary) the use of EDT features to ensure that only certain subscribers (eg, subscribers authorised by subscription) can benefit from the EDT features.

[0027] Furthermore, since mobile network operators may expose EDT to service providers as a service capability, third-party service providers desire to be able to query the status of EDT, or enable / disable the EDT feature for each UE.

[0028] Therefore, an object of the present invention is to provide a UE, a core network node, an access network node, a transmission control method, and a control method for solving the problem that it is difficult to appropriately control EDT.

[0029] Solutions for solving problems

[0030] To achieve this objective, a user equipment (UE) as one aspect of the present invention includes a receiver and a hardware processor. The receiver is configured to receive a parameter from an access network node indicating whether the UE is restricted or authorized to send user data in a message sent on an uplink synchronization channel (UL-SCH). The hardware processor is configured to process instructions to determine whether to restrict or authorize sending user data in the message based on the parameter.

[0031] In addition, as another aspect of the present invention, the core network node includes a memory and at least one processor. The memory is used to store instructions. The processor is configured to process the instructions to determine whether the UE is restricted or authorized to send user data in the message sent on the UL-SCH.

[0032] In addition, the access network node as another aspect of the present invention includes a transmitter. The transmitter is configured to: send a parameter to a UE indicating whether the UE is restricted or authorized to send user data in a message sent on a UL-SCH; and send information of a permitted packet size used to send user data in the message.

[0033] In addition, the method used by the UE as another aspect of the present invention includes: receiving a parameter from an access network node for indicating whether the UE is restricted or authorized to send user data in a message sent on the UL-SCH; and processing instructions to determine whether the UE is restricted or authorized to send user data in the message based on the parameter.

[0034] In addition, a method used by a core network node as another aspect of the present invention includes: storing instructions; and processing the instructions to determine whether the UE is restricted or authorized to send user data in a message sent on the UL-SCH.

[0035] In addition, the method used by the access network node as another aspect of the present invention includes: sending a parameter to the UE to indicate whether the UE is restricted or authorized to send user data in a message sent on the UL-SCH; and sending information on the permitted packet size used to send user data in the message.

[0036] In addition, a system as another aspect of the present invention includes a UE and an access network node. The UE includes the configuration of the above aspect of the present invention. The access network node includes the configuration of the above aspect of the present invention.

[0037] Effects of the Invention

[0038] With the configuration described above, the present invention can provide a UE, a core network node, an access network node, a transmission control method, and a control method for solving the problem that it is difficult to appropriately control EDT. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 is a diagram showing an example of contention-based random access.

[0040] Figure 2 is a diagram showing an example of a call flow that allows data transmission.

[0041] Figure 3 The network's EDT restriction / authorization control during the registration procedure, attach procedure or TAU / RAU procedure is shown.

[0042] Figure 4 Demonstrates EDT restriction / authorization control by service operators via NEF / SCEF.

[0043] Figure 5 EDT paging with controlled EDT usage is demonstrated.

[0044] Figure 6 EDT congestion control in RAN node 5 is shown.

[0045] Figure 7 Situations where EDT is prohibited within a whole cell, a group of cells, a registration area or the whole public land mobile network (PLMN) are shown.

[0046] Figure 8 A mobile (cellular or wireless) telecommunication system 1 is schematically shown.

[0047] Fig. 9 is a block diagram showing the main components of a UE.

[0048] Fig.10 is a block diagram showing the main components of the RAN node 5 .

[0049] Fig.11 is a block diagram illustrating the main components of an exemplary core network node. DETAILED DESCRIPTION

[0050] <First Exemplary Aspect>

[0051] Figures 3 to 7 Some exemplary ways in which the above problems may be solved are schematically shown. Figure 8 A cellular telecommunication system is schematically shown to which the technique proposed in this document may be applicable. Figures 9 to 11 yes Figures 1 to 8 Schematic block diagram of some nodes shown.

[0052] Solution 1: EDT restriction / authorization control of the network

[0053] Solution 1 proposes EDT restriction / authorization control of the network. EDT restriction / authorization control will enable the network (i.e., network operator) to restrict or authorize the use of EDT for each UE 3 or each UE group. In order to restrict or authorize EDT for a specific UE, it is proposed to introduce a new subscription parameter called EDT restriction parameter (or EDT authorization parameter or EDT prohibition parameter or any other parameter name for the purpose of authorizing or restricting the use of EDT for 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 HLR10 and specifies whether the EDT function is restricted or authorized (i.e., whether it is allowed or not allowed) for UE 3 for each public land mobile network (PLMN). The EDT restriction / authorization parameter can be configured in the UDM / UDR, HSS or HLR 10 via the operation and maintenance (O&M) module. In addition, the third party service provider can query or enable / disable EDT restriction / authorization parameters in UDM / UDR, HSS or HLR 10 via the network exposure function (NEF) or service capability exposure (SCEF) 13.

[0054] Figure 3 The network's EDT restriction / authorization control during registration, attach or TAU / RAU procedures is demonstrated.

[0055] 1a) If the UE 3 is capable of EDT and the UE 3 supports the EDT restriction / authorization functionality (e.g. by subscribing to EDT restriction / authorization support), the UE 3 indicates to the AMF / MME / SGSN 9 its ability to support EDT restriction / authorization (e.g. for the RAT (Radio Access Technology) on which the UE 3 is camped) in an appropriately formatted Registration Request, Attach Request or TAU / RAU Request message (and / or any other suitable NAS message).

[0056] On the other hand, the UE 3 may indicate its EDT capability feature support (e.g., an indication that the UE 3 is capable of EDT) in an appropriately formatted Registration Request, Attach Request or TAU / RAU Request message (and / or any other suitable NAS message). In this case, the EDT feature support indication may be interpreted by the AMF, MME or SGSN 9 as whether the UE 3 is capable of EDT and whether the UE 3 also supports EDT restriction / authorization processing.

[0057] 1b) The UE 3 may, optionally, indicate its support for EDT restriction / authorization indirectly to the AMF / MME / SGSN 9 via the RAN node 5 (e.g. base station, gNB, eNB or RNC) in the following manner: first indicating to the RAN node 5 (gNB, eNB or RNC) in an RRC message (e.g. an appropriately formatted RRC Connection Request or RRC Connection Setup Complete or any other suitable AS message), and then the RAN node 5 forwards the EDT restriction / authorization support parameters to the AMF / MME / SGSN 9 within an appropriate N2-AP / S1-AP UE Initialization message or within any other suitable (existing or new) message on the N2 / S1 interface between the RAN node 5 and the AMF / MME / SGSN 9.

[0058] On the other hand, UE 3 may indicate its EDT capability feature support (e.g., an indication that UE 3 is capable of EDT) in RRC Connection Request or RRC Connection Setup Complete or any other AS message and thus in N2-AP / S1-AP UE Initial message. In this case, the EDT feature support indication may be interpreted by the AMF, MME or SGSN 9 as whether UE 3 is capable of EDT and whether UE 3 also supports EDT restriction / authorization processing.

[0059] 2) If the AMF / MME / SGSN 9 does not have the subscription information of the UE 3, the AMF / MME / SGSN 9 may make a UE subscription query to the UDM / UDR, HSS or HLR 10 for the UE 3 (e.g., via an update location request / confirmation procedure or any other procedure for retrieving / querying UE subscription information from the UDM / UDR, HSS or HLR 10). This includes the EDT restriction / authorization subscription parameter of the UE 3. This parameter is maintained in the UDM / UDR, HSS or HLR 10 as part of the subscription data and specifies whether the EDT function is restricted for the UE 3. The restriction / authorization of EDT may be for each RAT within the PLMN, for each PLMN, or for all PLMNs (including the user's HPLMN).

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

[0061] 4) If the UE 3 is capable of EDT and the UE indicates support for EDT restriction / authorization in step 1 via NAS or AS message, then whenever the UE context is established (for example, during the service request procedure, registration procedure, attach procedure and TAU / RAU procedure), 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 on the AMF / gNB interface, MME / eNB interface or SGSN / RNC interface): whether the UE 3 is restricted or authorized to use the EDT feature in the RAN network (based on the EDT restriction / authorization parameter value from the UDM / UDR, HSS or HLR 10).

[0062] The AMF / MME / SGSN 9 also includes the Registration / Attach / TAU / RAU Accept message in the N2-AP / S1-AP Initial Context Setup Request message to the RAN node 5 or in the downlink NAS transport message. If the UE 3 includes support for EDT restriction / authorization in step 1, the AMF / MME / SGSN 9 includes the EDT restriction / authorization parameters in the Registration Accept message / Attach Accept message / TAU Accept message / RAU Accept message or any other NAS message to the UE 3.

[0063] The EDT restriction / authorization parameter may take values ​​such as "EDT restricted / not restricted", "EDT prohibited / not prohibited", "EDT authorized / not authorized", "Use CIoT C-plane mechanism instead of EDT", "Use CIoT U-plane mechanism instead of EDT" or "EDT temporarily unavailable". If EDT is temporarily unavailable due to any reason in EPC or 5GC (e.g. AMF / MME / SGSN 9 congestion or NEF / SCEF13 congestion), the AMF / MME / SGSN 9 may include an EDT back-off timer to indicate how long the use of EDT is restricted. In the case where the AMF / MME / SGSN 9 indicates "EDT temporarily unavailable" to the UE 3 but there is no EDT back-off timer, the UE 3 may use the back-off timer value of the "CIoT C-plane back-off timer" if this information is available in the Registration Accept message / Attach Accept message / TAU Accept message / RAU Accept message or any other NAS message.

[0064] 5) The RAN node 5 forwards the received NAS message (eg 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 suitable RRC message.

[0065] 6) The UE 3 is configured to use the received value of the EDT restriction / authorization parameter to determine whether the EDT feature is restricted or authorized (eg, allowed or not allowed, prohibited or not prohibited).

[0066] If the UE 3 is capable of EDT, the UE 3 assumes that the EDT feature is allowed unless explicitly restricted / prohibited by the network.

[0067] If the EDT feature is restricted / prohibited by the network, UE 3 does not attempt EDT until the network explicitly lifts the EDT restriction (eg, in signaling to UE 3) or UE 3 moves to another RAT or PLMN.

[0068] If the EDT feature is restricted and an EDT back-off timer is included, the UE 3 does not attempt to perform EDT until the EDT back-off timer expires.

[0069] Figure 4 The service operator's EDT restriction / authorization control via NEF / SCEF 13 is shown.

[0070] 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 parameter name with the same purpose) indicates whether the request is to query the status of the EDT feature (e.g., whether it is restricted) or whether to enable / disable the EDT restriction / authorization subscription parameter in the UDM / UDR, HSS or HLR 10 for a specific UE or UE group.

[0071] 2. The NEF / SCEF 13 stores the SCS / AS identifier. The NEF / SCEF 13 assigns the NEF / SCEF Reference ID. Based on the operator policy, if the SCS / AS 12 is not authorized to make the request (e.g., if the SLA does not allow the request) or the SCS / AS 12 has exceeded its quota or rate for submitting EDT requests, the NEF / SCEF 13 returns an EDT Response (as shown in step 9) and provides a value in the EDT Result parameter that appropriately indicates a failure result.

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

[0073] 4. The UDM / UDR, HSS or HLR 10 checks the EDT request message (e.g., whether the serving AMF / MME / SGSN 9 supports the EDT restriction / authorization feature). If the check fails, the UDM / UDR, HSS or HLR 10 returns an EDT response message at step 8 and provides a value indicating failure in the EDT result parameter to the NEF / SCEF 13.

[0074] If the EDT request is to obtain the current status of the EDT restriction / authorization parameters in the UDM / UDR, HSS or HLR 10, the UDM / UDR, HSS or HLR 10 checks the values ​​of the EDT restriction / authorization parameters and returns an EDT response message at step 8. In the EDT result parameter, the UDM / UDR, HSS or HLR 10 includes information related to the EDT restriction - whether the use of the EDT feature is restricted (e.g., whether it is enabled or disabled).

[0075] 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 in the UDM / UDR, HSS or HLR 10 to an appropriate value (eg, EDT allowed or not allowed).

[0076] 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 within the AMF / MME / SGSN context (enable or disable the use of the EDT feature).

[0077] 6. Based on operator policy, AMF / MME / SGSN 9 may reject the request (e.g., overload or UDM / UDR, HSS or HLR 10 has exceeded its quota or rate for submitting EDT limit / authorization requests).

[0078] The AMF / MME / SGSN 9 updates the EDT restriction / authorization parameters in the AMF / MME / SGSN context. For example, the AMF / MME / SGSN 9 may be configured to transmit the EDT restriction / authorization parameters as part of its context information during an AMF / MME / SGSN change.

[0079] The AMF / MME / SGSN 9 updates the EDT restriction / authorization parameters in the UE at the next TAU / RAU, or based on local operator policy, the network may detach the UE indicating the need to reattach.

[0080] 7. If the EDT restriction / authorization is 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 the success or failure of updating the EDT restriction / authorization parameters in the AMF / MME / SGSN context.

[0081] 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.

[0082] 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 an EDT Request message is sent in step 1 to query the status of the EDT restriction / authorization parameters in the UDM / UDR, HSS or HLR 10, the EDT Result parameter indicates the status of the EDT restriction / authorization parameters in the UDM / UDR, HSS or HLR 10 - EDT Allowed or EDT Not Allowed.

[0083] Figure 5 EDT paging with controlled EDT usage is demonstrated.

[0084] 1. The AMF / MME / SGSN 9 receives a Downlink Data Indication (DDI) requesting Early Data Transmission (EDT) in the downlink (EDT paging, or any other indication or parameter name meaning paging for downlink EDT). The AMF / MME / SGSN 9 stores the received indication for EDT paging. If the EDT restriction / authorization parameter in the AMF / MME / SGSN context is not set to restricted (e.g., the EDT restriction / authorization parameter is not set to restricted), the AMF / MME / SGSN 9 includes the EDT paging parameters in each subsequent paging message to all gNBs / eNBs / RNCs 5 selected by the AMF / MME / SGSN 9 for paging.

[0085] 2. If the AMF / MME / SGSN 9 does not have information (EDT restriction / authorization parameters) on whether the paged UE 3 is authorized (i.e., not restricted) for the use of EDT, the AMF / MME / SGSN 9 makes a subscription query to the UDM / UDR, HSS or HLR 10 to retrieve the UE's subscription information (e.g., via an update location request / confirmation procedure or any other procedure for UE subscription information retrieval / query from the UDM / UDR, HSS or HLR 10).

[0086] 3. If the paged UE 3 is authorized for EDT (eg, the UE 3's use of EDT is not restricted via subscription parameters such as EDT restriction / authorization), the AMF / MME / SGSN 9 decides to page the UE 3 for EDT.

[0087] 4. The AMF / MME / SGSN 9 sends a paging request to the connected RAN node 5, where together with the UE ID, the AMF / MME / SGSN 9 includes an EDT paging parameter (or any other parameter name) for indicating that the paging is for EDT.

[0088] 5. The RAN node 5 forwards the paging request on a system information broadcast message, wherein the paging message is broadcast with the EDT paging parameters included therein.

[0089] A mobile terminal capable of EDT and being paged for EDT (i.e., with EDT paging parameters in the paging message) is configured to respond to the paging and follow the procedure used for EDT data transmission (e.g., using the PRACH preamble code designated for EDT) and transmit data (e.g., data PDU or NAS data) within Msg2 (RRC Connection / Connectionless Request message).

[0090] Figure 6 EDT congestion control in a RAN node 5 (e.g., eNB / gNB) is shown.

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

[0092] 1. UE 3 sends a suitably formatted Msg1, such as a random access preamble.

[0093] 2. If PRACH resources in the RAN are scarce, the RAN sends a suitably formatted Msg2 with a RAR uplink grant and "grant packet size for EDT" to the UE 3.

[0094] 3. If the "granted packet size for EDT" is specified in the RAN in Msg2 (Random Access Response message), the UE 3 compares the "granted packet size for EDT" received from the RAN with the user data to be sent from the UE 3 upper layer to decide whether the UE 3 can send the user data in Msg3 (e.g., RRC Connection Request or EDT Data Request or any other message name with the purpose of EDT). If the user data in the UE 3 is larger than the "granted packet size for EDT", the UE 3 uses an appropriately formatted Msg5 (e.g., RRC Connection Setup Complete) or uses data sent via the user plane back to the conventional CIoT MO (mobile originated) process.

[0095] In conclusion, Figure 6 A use case is shown in which UE 3 transmits Msg3 with EDT data because the size of user data to be transmitted is smaller than the "grant packet size for EDT" in the Msg2 random access response.

[0096] Figure 7 The case where EDT is prohibited in a whole cell, a group of cells, a registration area or a whole PLMN is shown. A network operator may wish to prohibit EDT for all UEs in a cell, a group of cells or a registration area.

[0097] 1) Based on the operator's policy or configuration in the AMF / MME / SGSN 9 or O&M module, the AMF / MME / SGSN 9 may indicate an EDT inhibit indication / parameter to the RAN node 5 in an appropriately formatted AMF / MME configuration command or N2-AP or S1-AP initial setup request message or any other suitable (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 inhibit indication / parameter (or any other indication / parameter name related to whether EDT should be inhibited) may take values ​​such as "EDT inhibited", "EDT not inhibited", etc. or any other value for controlling the restriction or authorization of the use of EDT by the UE. The AMF / MME / SGSN 9 may indicate the EDT inhibit indication to one RAN node, a group of RAN nodes, or all RAN nodes within a registration area. If the included EDT disable indication is set to "on" (ie EDT is disabled), the AMF / MME / SGSN 9 may also include in the same N2 / S1 message an EDT back-off timer defining how long EDT is disabled.

[0098] 2) When the RAN node 5 receives an EDT prohibit indication in an N2 / S1 message from the AMF / MME / SGSN 9 (for example, an AMF / MME configuration command message or an N2-AP / S1-AP initial setup request message or any other message from the AMF / MME / SGSN 9), the RAN node 5 saves the received EDT prohibit indication and sets the EDT prohibit indication in the SI broadcast to reflect the EDT prohibit indication from the AMF / MME / SGSN 9.

[0099] If an EDT back-off timer is included, the RAN node 5 continues to broadcast the EDT inhibit state until the EDT back-off timer expires or until a new EDT indication is received from the AMF / MME / SGSN 9 resetting the inhibit state (eg, allowing the UE to use EDT).

[0100] If no EDT back-off timer is included, the RAN node 5 continues to broadcast the EDT prohibited state until a new EDT indication is received from the AMF / MME / SGSN 9 resetting the prohibited state (eg allowing the UE to use EDT).

[0101] 3) When the UE 3 in idle mode reads system information:

[0102] - If the EDT indication / parameter in the system information (SI) indicates that EDT is disabled, the UE 3 will not initiate data transmission via EDT until the EDT indication in the SI indicates the disabled state;

[0103] - If the EDT indication / parameters in the system information (SI) indicate that EDT is not prohibited or there is no EDT status indication at all, the UE 3 may initiate data exchange via EDT, unless EDT is not restricted in any other way.

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

[0105] Summarize

[0106] Advantageously, the above exemplary aspects include, but are not limited to, one or more of the following functions:

[0107] 1) A new subscription parameter in UDM / UDR, HSS or HLR, called EDT restriction parameter (or EDT authorization parameter or any other parameter name for authorizing or restricting the use of EDT by the UE).

[0108] 2) The UE indicates its support for EDT or its support for EDT restriction or authorization in an appropriately formatted NAS message (e.g., REGISTRATION, ATTACH, TAU / RAU REQUEST message) to the AMF / MME / SGSN.

[0109] 3) 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 to obtain UE subscription information.

[0110] 4) If the UE includes support for EDT limitation / authorization in the registration / attach / TAU / RAU request, the AMF / MME / SGSN provides the EDT limitation / authorization parameters to the UE in the registration accept message / attach accept message / TAU accept message / RAU accept message or any other NAS message.

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

[0112] 6) If the UE is capable of EDT and the UE is not restricted by a subscription for EDT use, then EDT paging is performed.

[0113] 7) The EDT resources granted in the random access response message and the UE's use of the EDT are not greater than the data sent using the granted resources of the EDT.

[0114] 8) Disable EDT within a cell, cell group, registration area or the entire PLMN via EDT disable indication / parameters broadcast in system information.

[0115] It can be seen that the above aspects describe a method, which includes one or more of the following steps:

[0116] 1) New subscription parameter definition in UDM / UDR, HSS or HLR, the new subscription parameter is called EDT restriction parameter (or EDT authorization parameter or any other parameter name for authorizing or restricting the use of EDT by UE).

[0117] 2) The UE indicates its support for EDT or its support for EDT restriction or authorization in NAS messages (e.g., REGISTRATION, ATTACH, TAU / RAU REQUEST messages) to the AMF / MME / SGSN.

[0118] 3) Optionally, the UE first indicates its support for EDT or its support for EDT restriction 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 the N2-AP / S1-AP UE Initial message or in any other existing or new message on the N2 / S1 interface between the RAN node and the AMF / MME / SGSN.

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

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

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

[0122] 7) If the UE is capable of EDT and the UE is not restricted by a subscription for EDT use, then EDT paging is performed.

[0123] 8) The EDT resource grant in the random access response message and the UE's use of the EDT are not greater than the data sent using the granted resources of the EDT.

[0124] 9) Disable EDT within a cell, cell group, registration area or the entire PLMN via EDT disable indication / parameters broadcast in system information.

[0125] It can be seen that the above aspects advantageously provide several benefits, including (but not limited to) the above benefits:

[0126] The proposed EDT restriction / authorization control will enable the network (i.e., network operator) to restrict or authorize the use of EDT for individual UEs or groups of UEs. In order to restrict or authorize EDT for specific UEs, it is proposed to introduce a new subscription parameter called the EDT restricted parameter in the UDM / UDR, HSS or HLR. In this way, the network operator will be able to prioritize the use of EDT in certain locations and times in the event that not all EDT capable UEs can utilize the EDT feature.

[0127] System Overview

[0128] Figure 8 There is schematically shown a mobile (cellular or wireless) telecommunication system 1 to which the above aspects apply.

[0129] In this network, users of mobile devices 3A-3C (or user equipment, or "UE") can communicate with each other and other users using 5G radio access technology (RAT) via corresponding base stations 5 and core network 7. It should be understood that multiple base stations 5 (or "gNB" in 5G networks, "eNB" in LTE) form a (radio) access network. It should be understood by those skilled in the art that although for illustration purposes only, the base stations 5 are described in detail below. Figure 8 Three mobile devices 3 and one base station 5 are shown, but the system will typically include other base stations and mobile devices when implemented. It should also be understood that the (radio) access network may also support E-UTRA radio access technology (e.g., as an alternative or in addition to 5G).

[0130] The core network 7 typically comprises logical nodes (or "functions") for supporting communications in the telecommunications system 1. Typically, for example, the core network 7 of a "next generation" / 5G system will include control plane functions and user plane functions, among other things.

[0131] As is well known, when a mobile device 3 moves around in the geographical area covered by the telecommunication system 1, the mobile device 3 may enter and leave the area (i.e., radio cell) served by a base station 5 or (R)AN. In order to track the mobile device 3 and facilitate movement between different base stations 5, the core network 7 includes at least one access and mobility management function (AMF) 9. The AMF 9 communicates with the base stations 5 connected to the core network 7. In some core networks, the functions of the AMF 9 may be performed by a mobility management entity (MME) or a serving GPRS support node (SGSN).

[0132] The core network 7 also includes UDM / UDR 10 (and / or HSS / HLR, if appropriate), one or more gateways 11 and / or one or more application functions (AF) 12, etc. Figure 8 Although not shown in the figure, the core network 7 may also include other nodes such as a network exposure function (NEF) and / or a service capability exposure function (SCEF).

[0133] The mobile device 3 and its corresponding serving base station 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface, etc.). Neighboring base stations 5 are connected to each other via appropriate base station to base station interfaces (such as the so-called "X2" interface and / or "Xn interface", etc.), directly or through an appropriate (home) base station gateway. Each base station 5 is also connected to the core network node 9 / 10 / 11 / 12 / 13 via an appropriate interface (such as the so-called "S1" and / or "N2" / "N3" interface, etc.). From the core network 7, a connection to an external IP network 20 (such as the Internet) is also provided.

[0134] User Equipment (UE)

[0135] Fig. 9 3 is a block diagram showing the main components of a UE (mobile device 3). As shown, the UE 3 includes transceiver circuitry 31 operable to send and receive signals to and from connected nodes via one or more antennas 32. Fig. 9 34, but the UE 3 will of course have all the common functions of a conventional mobile device (such as a user interface 35), and the functions may be appropriately provided by any one or any combination of hardware, software and firmware. For example, the software may be pre-installed in the memory 34 and / or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The controller 33 controls the operation of the UE 3 according to the software stored in the memory 34. The software includes an operating system 341 and a communication control module 342 having at least a transceiver control module 3421, etc. The communication control module 342 (using its transceiver control module 3421) is responsible for processing (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 signalling may, for example, comprise appropriately formatted signalling messages related to EDT restriction / authorisation control (for UE 3) (e.g. registration request and related responses), and in particular registration request, attach request or TAU / RAU request messages (or any other NAS messages) and / or signalling messages related to random access procedures.

[0136] RAN Node

[0137] Fig.101 is a block diagram showing the main components of a RAN node 5 (RNC or base station, such as eNB / gNB). As shown, the RAN node 5 includes a transceiver circuit 51 that is operable to send signals to and receive signals from a UE 3 via one or more antennas 52, and is operable to send signals to and receive signals from a core network node 9 / 10 / 11 / 12 / 13 via a network interface 55 (e.g., S1 / N2 / N3). The transceiver circuit 51 can also be operable to send signals to and receive signals from other base stations via the network interface 55 (via, for example, an X2 or Xn interface). The controller 53 controls the operation of the RAN node 5 according to the software stored in the memory 54. For example, the software can be pre-installed in the memory 54 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 541 and a communication control module 542 having at least a transceiver control module 5421, etc. The communication control module 542 (using its transceiver control module 5421) is responsible for processing (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, where appropriate). Such signaling may, for example, include appropriately formatted signaling messages for EDT restriction / authorization control.

[0138] Core network nodes

[0139] Fig.111 is a block diagram showing the main components of an exemplary core network node 9 / 10 / 11 / 12 / 13. As shown, the core network node 9 / 10 / 11 / 12 / 13 includes a transceiver circuit 91 / 101 / 111 / 121 / 131 that can send signals to other network nodes and receive signals from other network nodes (directly or indirectly) via a network interface 94 / 104 / 114 / 124 / 134. The controller 92 / 102 / 112 / 122 / 132 controls the operation of the core network node 9 / 10 / 11 / 12 / 13 according to the software stored in the memory 93 / 103 / 113 / 123 / 133. For example, the software can be pre-installed in the memory 93 / 103 / 113 / 123 / 133 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software comprises an operating system 931 / 1031 / 1131 / 1231 / 1331 and a communication control module 932 / 1032 / 1132 / 1232 / 1332 having at least a transceiver control module 9321 / 10321 / 11321 / 12321 / 13321, etc. The communication control module 932 / 1032 / 1132 / 1232 / 1332 (using its transceiver control module 9321 / 10321 / 11321 / 12321 / 13321) is responsible for (directly or indirectly) processing (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, etc. The signaling may, for example, comprise appropriately formatted signaling messages for EDT restriction / authorization control. In case the core network node 9 / 10 / 11 / 12 / 13 provides the functionality of UDM / UDR, HSS or HLR, it may be configured to store new subscription parameters referred to herein as EDT restriction parameters (or EDT authorization parameters or EDT prohibition parameters or any other parameter name for the purpose of authorizing or restricting the use of EDT by the UE).

[0140] Modifications and Replacements

[0141] Detailed aspects have been described above. As will be appreciated by those skilled in the art, multiple modifications and substitutions may be made to the above aspects while still benefiting from the invention implemented therein. By way of illustration, only some of these alternatives and modifications will now be described.

[0142] In the above description, for ease of understanding, the UE, RAN node and core network node are described as having multiple discrete modules (such as communication control modules). Although these modules can be provided in this way for certain applications (for example, existing systems have been modified to implement applications of the present invention), in other applications (for example, in systems designed from the outset with the features of the present invention in mind), these modules can be built into the overall operating system or code, so these modules may not be identified as discrete entities. These modules can also be implemented in the form of software, hardware, firmware or a combination thereof.

[0143] Each controller may include any suitable form of processing circuitry, including (but not limited to) for example: one or more hardware-implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memory / cache (program and / or data); processing registers; a communication bus (e.g., a control bus, a data bus, and / or an address bus); direct memory access (DMA) functionality; and / or hardware or software-implemented counters, pointers, and / or timers, etc.

[0144] In the above aspects, a plurality of software modules are described. As will be appreciated by those skilled in the art, the software modules may be provided in compiled or uncompiled form and may be provided to the UE, RAN node and core network node as a signal over a computer network or on a recording medium. In addition, the functions performed by part or all of the software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred because it facilitates updating the UE, RAN node and core network node to update their functionality.

[0145] In the above aspect, 3GPP radio communication (radio access) technology is used. However, according to the above aspect, any other radio communication technology (eg, WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) may also be used.

[0146] Items of user equipment may include, for example, communication devices such as mobile phones, smart phones, user equipment, personal digital assistants, laptops / tablets, web browsers and / or e-book readers. Such mobile (or even generally fixed) devices are typically operated by a user, but so-called "Internet of Things" (IoT) devices and similar machine type communication (MTC) devices may also be connected to a network. For simplicity, the present application refers to mobile devices (or UEs) in the specification, but it should be understood that the described techniques may be implemented on any communication device (mobile and / or generally fixed) that is capable of connecting to a communication network to send / receive data, whether such communication device is controlled by manual input or by software instructions stored in a memory.

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

[0148] Abbreviations and terms

[0149] The following abbreviations and terms are used in the current literature:

[0150] 3GPP Third Generation Partnership Project

[0151] 5G-AN 5G Access Network

[0152] 5G-RAN 5G Radio Access Network

[0153] 5GS 5G System

[0154] AF Application Function

[0155] AMF Access and Mobility Management Function

[0156] AS Access Layer

[0157] AUSF certification and safety features

[0158] CIoT Cellular Internet of Things

[0159] CP Control Plane

[0160] DL Downlink

[0161] DNN data network name

[0162] EDT Early Data Transmission

[0163] EPS Evolved Packet System

[0164] HARQ Hybrid Automatic Repeat Request

[0165] HLR Home Location Register

[0166] HSS Home Subscriber Server

[0167] eMTC Enhanced Machine Type Communication

[0168] eNB Enhanced NodeB

[0169] gNB Next Generation NodeB

[0170] MAC Medium Access Control

[0171] ME Mobile Devices

[0172] MME Mobility Management Entity

[0173] NB-IoT Narrowband Internet of Things

[0174] NAS Non-Access Stratum

[0175] NF Network Function

[0176] NEF Network Exposure Function

[0177] NR New Radio

[0178] O&M Operation and Maintenance

[0179] PCF Policy Control Function

[0180] SCEF service capability exposure function

[0181] SGSN Serving GPRS Support Node

[0182] PRACH Physical Random Access Channel

[0183] (R)AN Radio Access Network

[0184] RAR Random Access Response

[0185] RAU Routing Area Update

[0186] RNC Radio Network Controller

[0187] RRC Radio Resource Control

[0188] SIB System Information Block

[0189] SIM Subscriber Interface Module

[0190] TAU Tracking Area Updates

[0191] UDM Unified Data Management

[0192] UDR Unified Data Repository

[0193] UE User Equipment

[0194] UL Uplink

[0195] Additional Notes

[0196] (Supplementary Note 1)

[0197] A user equipment, namely, UE, includes:

[0198] a receiver configured to receive, from an access network node, a parameter indicating whether the UE is restricted or authorized to transmit user data in a message transmitted on an uplink synchronization channel (UL-SCH); and

[0199] A hardware processor is configured to process instructions to determine whether to be restricted or authorized to send the user data in the message based on the parameter.

[0200] (Supplementary Note 2)

[0201] The UE according to Supplementary Note 1 further comprises: a transmitter configured to send information of a capability of sending the user data in the message to a core network node via the access network node,

[0202] The receiver is further configured to receive the parameter after sending the information of the capability of sending the user data in the message.

[0203] (Supplementary Note 3)

[0204] The UE according to Supplementary Note 1, further comprising: a transmitter configured to send information supporting the capability of limiting or authorizing the sending of the user data in the message to a core network node via the access network node,

[0205] The receiver is further configured to receive the parameter based on information supporting a capability to restrict or authorize sending the user data in the message.

[0206] (Supplementary Note 4)

[0207] The UE according to Supplementary Note 3, wherein the parameter for indicating whether the UE is restricted or authorized to send the user data in the message is based on a UE context updated by the core network node.

[0208] (Supplementary Note 5)

[0209] The UE according to any one of Supplementary Notes 1 to 4, wherein whenever a UE context is established, a parameter for indicating whether the UE is restricted or authorized to send the user data in the message is indicated.

[0210] (Supplementary Note 6)

[0211] The UE according to Supplementary Note 1, wherein:

[0212] A parameter for indicating whether the UE is restricted or authorized to send the user data in the message is broadcast from the access network node;

[0213] The receiver is further configured to receive information of a permitted packet size for sending the user data in the message; and

[0214] The hardware processor is further configured to determine whether the UE sends the user data based on the information of the allowed packet size for sending the user data in the message.

[0215] (Supplementary Note 7)

[0216] The UE according to Supplementary Note 1, wherein:

[0217] A parameter for indicating whether the UE is restricted or authorized to send the user data in the message is broadcasted from the access network node; and

[0218] The parameter used to indicate whether the UE is restricted or authorized to send the user data in the message indicates prohibition of the sending.

[0219] (Supplementary Note 8)

[0220] A UE according to any one of Supplementary Notes 1 to 7, wherein:

[0221] The receiver is further configured to receive a parameter indicating whether the UE is restricted or authorized to send the user data in the message, and a value of a back-off timer used to send the user data; and

[0222] The hardware processor is further configured to process instructions to determine whether the UE sends the user data in the message based on a value of the back-off timer.

[0223] (Supplementary Note 9)

[0224] The UE according to Supplementary Note 8, wherein the hardware processor is further configured to not attempt to send the user data in the message until the UE moves to another radio access technology (RAT) or the core network node lifts restrictions on sending the user data in the message.

[0225] (Supplementary Note 10)

[0226] A UE according to any one of Supplementary Notes 1 to 7, wherein:

[0227] The receiver is further configured to receive a value "Early Data Transmission (EDT) is temporarily unavailable" from the core network node; and

[0228] The hardware processor is also configured to not attempt to send the user data in the message until a backoff timer used by a cellular Internet of Things control plane, i.e., a CIoT control plane, in the UE expires.

[0229] (Supplementary Note 11)

[0230] A core network node, comprising:

[0231] A storage component for storing instructions; and

[0232] At least one processor is configured to process instructions to determine whether a user equipment (UE) is restricted or authorized to send user data in a message sent on an uplink synchronization channel (UL-SCH).

[0233] (Supplementary Note 12)

[0234] The core network node according to Supplementary Note 11 further includes: a transmitter configured to send a parameter to the UE via the access network node for indicating whether the UE is restricted or authorized to send the user data in the message.

[0235] (Supplementary Note 13)

[0236] The core network node according to Supplementary Note 12 further includes: a receiver configured to receive information about a capability of sending the user data in the message from the UE via the access network node,

[0237] The transmitter is further configured to send the parameter based on information of the capability of sending the user data in the message.

[0238] (Supplementary Note 14)

[0239] The core network node according to Supplementary Note 12 further includes: a receiver configured to receive, from the UE via the access network node, information supporting the ability to restrict or authorize the sending of the user data in the message,

[0240] The transmitter is further configured to send the parameter based on information supporting limiting or authorizing the ability to send the user data in the message.

[0241] (Supplementary Note 15)

[0242] The core network node according to Supplementary Note 14, wherein:

[0243] The transmitter is further configured to send a request for subscription information corresponding to the UE to a subscription data server; and

[0244] The receiver is further configured to receive a parameter indicating whether the UE is restricted or authorized to send the user data in the message.

[0245] (Supplementary Note 16)

[0246] The core network node according to any one of Supplementary Notes 12 to 15, wherein the receiver is further configured to receive an insert subscriber data request from a server for subscription data,

[0247] The core network node further comprises: a hardware processor configured to process instructions to update a parameter indicating whether the UE is restricted or authorized to send the user data in the message,

[0248] The transmitter is further configured to send updated parameters to the UE.

[0249] (Supplementary Note 17)

[0250] The core network node according to Supplementary Note 11 further includes:

[0251] A receiver configured to receive a downlink data indication (DDI) from a network node for user plane data requesting that the user data be sent in the message; and

[0252] A transmitter is configured to send a paging request to the UE to send the user data in the message based on a result of determining whether the UE is restricted or authorized to send the user data in the message.

[0253] (Supplementary Note 18)

[0254] A core network node according to any one of Supplementary Notes 12 to 16, wherein:

[0255] The parameter indicating whether the UE is restricted or authorized to send the user data in the message indicates prohibition of the sending;

[0256] The transmitter is further configured to send a configuration command including a parameter for indicating prohibition of the sending to the access network node; and

[0257] The access network node is further configured to broadcast at least to the UE a parameter indicating prohibition of the sending.

[0258] (Supplementary Note 19)

[0259] An access network node comprises a transmitter, wherein the transmitter is configured to: send a parameter to a user equipment (UE) for indicating whether the UE is restricted or authorized to send user data in a message sent on an uplink synchronization channel (UL-SCH); and send information of an allowed packet size used for sending the user data in the message.

[0260] (Supplementary Note 20)

[0261] A method used by a user equipment (UE), comprising:

[0262] receiving from an access network node a parameter indicating whether the UE is restricted or authorized to transmit user data in a message transmitted on an uplink synchronization channel (UL-SCH); and

[0263] The processing instructions are to determine whether to be restricted or authorized to send the user data in the message based on the parameter.

[0264] (Supplementary Note 21)

[0265] The method according to Supplementary Note 20, further comprising:

[0266] sending, via the access network node, to a core network node, information of a capability to send the user data in the message; and

[0267] After sending the information of the capability to send the user data in the message, the parameters are received.

[0268] (Supplementary Note 22)

[0269] The method according to Supplementary Note 20, further comprising:

[0270] sending, via the access network node, to a core network node, information supporting a capability to restrict or authorize sending the user data in the message; and

[0271] The parameter is received based on information supporting limiting or authorizing the ability to send the user data in the message.

[0272] (Supplementary Note 23)

[0273] The method according to supplementary note 22, wherein the parameter for indicating whether the UE is restricted or authorized to send the user data in the message is based on a UE context updated by the core network node.

[0274] (Supplementary Note 24)

[0275] The method according to any one of Supplementary Notes 20 to 23, wherein whenever a UE context is established, a parameter for indicating whether the UE is restricted or authorized to send the user data in the message is indicated.

[0276] (Supplementary Note 25)

[0277] The method according to Supplementary Note 20, wherein a parameter for indicating whether the UE is restricted or authorized to send the user data in the message is broadcast from the access network node, the method further comprising:

[0278] receiving information of a permitted packet size for sending said user data in said message; and

[0279] It is determined whether the UE sends the user data based on the information of the allowed packet size used for sending the user data in the message.

[0280] (Supplementary Note 26)

[0281] The method according to Supplementary Note 20, wherein:

[0282] A parameter for indicating whether the UE is restricted or authorized to send the user data in the message is broadcasted from the access network node; and

[0283] The parameter used to indicate whether the UE is restricted or authorized to send the user data in the message indicates prohibition of the sending.

[0284] (Supplementary Note 27)

[0285] The method according to any one of Supplementary Notes 20 to 26, further comprising:

[0286] receiving a parameter indicating whether the UE is restricted or authorized to send the user data in the message, and a value of a backoff timer used to send the user data; and

[0287] The processing instruction is to determine whether the UE sends the user data in the message based on the value of the back-off timer.

[0288] (Supplementary Note 28)

[0289] The method according to Supplementary Note 27 further comprises: not attempting to send the user data in the message until the UE moves to another radio access technology (RAT) or the core network node lifts restrictions on sending the user data in the message.

[0290] (Supplementary Note 29)

[0291] The method according to any one of Supplementary Notes 20 to 26, further comprising:

[0292] receiving a value “Early Data Transmission (EDT) temporarily unavailable” from the core network node;

[0293] Do not attempt to send the user data in the message until the backoff timer used by the cellular Internet of Things control plane, i.e., the CIoT control plane, in the UE expires.

[0294] (Supplementary Note 30)

[0295] A method used by a core network node, comprising:

[0296] storing instructions; and

[0297] The instructions are processed to determine whether a user equipment, UE, is restricted or authorized to send user data in a message sent on an uplink synchronization channel, UL-SCH.

[0298] (Supplementary Note 31)

[0299] The method according to Supplementary Note 30 further comprises: sending, via an access network node, to the UE a parameter for indicating whether the UE is restricted or authorized to send the user data in the message.

[0300] (Supplementary Note 32)

[0301] The method according to Supplementary Note 31, further comprising:

[0302] receiving, from the UE via the access network node, information on a capability to send the user data in the message; and

[0303] The parameters are sent based on information of the capability to send the user data in the message.

[0304] (Supplementary Note 33)

[0305] The method according to Supplementary Note 31, further comprising:

[0306] receiving, from the UE via the access network node, information supporting a capability to restrict or authorize sending the user data in the message; and

[0307] The parameters are sent based on information supporting limiting or authorizing the ability to send the user data in the message.

[0308] (Supplementary Note 34)

[0309] The method according to Supplementary Note 33, further comprising:

[0310] Sending a request for subscription information corresponding to the UE to a subscription data server; and

[0311] A parameter is received indicating whether the UE is restricted or authorized to send the user data in the message.

[0312] (Supplementary Note 35)

[0313] The method according to any one of Supplementary Notes 31 to 34, further comprising:

[0314] receiving an insert subscriber data request from a server that subscribes to the data;

[0315] processing instructions to update a parameter indicating whether the UE is restricted or authorized to send the user data in the message; and

[0316] The updated parameters are sent to the UE.

[0317] (Supplementary Note 36)

[0318] The method according to Supplementary Note 30, further comprising:

[0319] receiving from a network node for user plane data a downlink data indication (DDI) requesting that the user data be sent in the message; and

[0320] A paging request for the UE to send the user data in the message is sent based on a result of determining whether the UE is restricted or authorized to send the user data in the message.

[0321] (Supplementary Note 37)

[0322] According to the method according to any one of Supplementary Notes 31 to 35, wherein the parameter used to indicate whether the UE is restricted or authorized to send the user data in the message indicates prohibition of the sending, the method further includes:

[0323] sending a configuration command including a parameter for indicating prohibition of the sending to the access network node; and

[0324] At least a parameter indicating prohibition of the sending is broadcasted to the UE.

[0325] (Supplementary Note 38)

[0326] A method used by an access network node comprises: sending a parameter to a user equipment (UE) for indicating whether the UE is restricted or authorized to send user data in a message sent on an uplink synchronization channel (UL-SCH); and sending information of an allowed packet size used to send the user data in the message.

[0327] (Supplementary Note 39)

[0328] A system includes a user equipment (UE) and an access network node, wherein:

[0329] The UE includes the configuration disclosed in Supplementary Note 1; and

[0330] The access network node includes the configuration disclosed in Supplementary Note 19.

[0331] This application is based upon and claims the benefit of priority from European patent application 17202452.3 filed on November 17, 2017, the disclosure of which is incorporated herein in its entirety by reference.

[0332] Description of Reference Numerals

[0333] 1 Telecommunications systems

[0334] 3 UE

[0335] 31 Transceiver Circuit

[0336] 32 Antenna

[0337] 33 Controller

[0338] 34 Memory

[0339] 341 Operating System

[0340] 342 Communication Control Module

[0341] 3421 Transceiver Control Module

[0342] 35 User Interface

[0343] 5 eNB and RAN nodes

[0344] 51 Transceiver Circuit

[0345] 52 Antenna

[0346] 53 Controller

[0347] 54 Memory

[0348] 541 Operating System

[0349] 542 Communication Control Module

[0350] 5421 Transceiver Control Module

[0351] 55 Network Interface

[0352] 7 Core Network

[0353] 9 AMF / MME / SGSN

[0354] 10 UDM / UDR / HSS / HLR

[0355] 11 SGW / PGW(GW)

[0356] 12 SCS / AS

[0357] 13 NEF / SCEF

[0358] 91 / 101 / 111 / 121 / 131 Transceiver Circuit

[0359] 92 / 102 / 112 / 122 / 132 Controllers

[0360] 93 / 103 / 113 / 123 / 133 Memory

[0361] 931 / 1031 / 1131 / 1231 / 1331 operating system

[0362] 932 / 1032 / 1132 / 1232 / 1332 Communication Control Module

[0363] 9321 / 10321 / 11321 / 12321 / 13321 Transceiver Control Module

[0364] 94 / 104 / 114 / 124 / 134 network interfaces

[0365] 20 External IP Network

Claims

1. A user equipment, namely, UE, include: A receiver configured to receive first information, second information, and third information from an access network node, wherein the first information indicates whether the UE is allowed to initiate early data transmission (EDT), the second information indicates a first size, and the third information indicates that the UE is allowed to send small uplink data by utilizing an EDT mechanism, In which, when the first information indicates that the UE is allowed to initiate the EDT, the size of the uplink data is smaller than the first size indicated by the second information, and the third information indicates that the UE is allowed to send the small uplink data by utilizing the EDT mechanism, the transmitter is configured to send the uplink data to the access network node in message 3 during the random access process.

2. The UE according to claim 1, in: The first information is broadcast from the access network node.

3. The UE according to claim 1 or 2, in, The transmitter is configured to transmit the uplink data using message 5 or using data transmission via a user plane if the size of the uplink data is larger than the first size indicated by the second information.

4. The UE according to claim 1, in, The transmitter is configured to send an attach request message including information indicating that the UE supports the EDT or a tracking area update request message (TAU request message) including the information to a core network device.

5. An access network node, include: a transmitter configured to send first information, second information and third information to a user equipment (UE), wherein the first information indicates whether the UE is allowed to initiate early data transmission (EDT), the second information indicates a first size, and the third information indicates that the UE is allowed to send small uplink data by using an EDT mechanism, In which, when the first information indicates that the UE is allowed to initiate the EDT, the size of the uplink data is smaller than the first size indicated by the second information, and the third information indicates that the UE is allowed to send the small uplink data by utilizing the EDT mechanism, the receiver is configured to receive the uplink data from the UE in message 3 during a random access process.

6. The access network node according to claim 5, in, The transmitter is configured to broadcast the first information.

7. The access network node according to claim 5 or 6, in, The receiver is configured to receive the uplink data using message 5 or using data transmission via a user plane if the size of the uplink data is larger than the first size indicated by the second information.

8. A method used by a user equipment (UE), the method include: receiving first information, second information, and third information from an access network node, wherein the first information indicates whether the UE is allowed to initiate early data transmission (EDT), the second information indicates a first size, and the third information indicates that the UE is allowed to send small uplink data by utilizing an EDT mechanism, In which, when the first information indicates that the UE is allowed to initiate the EDT, the size of the uplink data is smaller than the first size indicated by the second information, and the third information indicates that the UE is allowed to send the small uplink data by utilizing the EDT mechanism, the method includes sending the uplink data to the access network node in message 3 during a random access process.

9. A method for accessing a network node, the method include: sending first information, second information and third information to a user equipment (UE), wherein the first information indicates whether the UE is allowed to initiate early data transmission (EDT), the second information indicates a first size, and the third information indicates that the UE is allowed to send small uplink data by using an EDT mechanism, In which, when the first information indicates that the UE is allowed to initiate the EDT, the size of the uplink data is smaller than the first size indicated by the second information, and the third information indicates that the UE is allowed to send the small uplink data by utilizing the EDT mechanism, the method includes receiving the uplink data from the UE in message 3 during a random access process.

Images