EU, NETWORK NODES FOR THE MANAGEMENT OF EU CATEGORY INFORMATION

Abstract

The present invention relates to a method carried out by a first network node (103). The first network node (103) determines which UE category a UE (101) belongs to. The UE category is M or non-BL in CE. The first network node (103) provides UE category information about the determined UE category to a second network node (105).

Description

EU, NETWORK NODES FOR THE MANAGEMENT OF EU CATEGORY INFORMATION TECHNICAL FIELD The modalities in this document generally refer to a user equipment (UE), a method carried out by the UE, a first network node, a method carried out by the first network node, a second network node, and a method carried out by the second network node. More particularly, the present invention relates to the handling of UE category information. BACKGROUND OF THE INVENTION LTE-M is short for Low Power Wide Area (LPWA) LTE-MTC. LTE stands for Long Term Evolution, and MTC stands for Machine-Type Communication. LTE-M is an evolving LPWA technology. It can also be described as LTE Category (Cat) MI, suitable for Internet of Things (IoT) UEs and / or Machine-to-Machine Communication (MTC) UEs and / or MTC IoT (MIoT). LTE-M networks can coexist with second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G) mobile networks, and also with any future generation of mobile networks. The LTE-M network can benefit from at least some of the security and privacy features of PLnfr / n / Lznz / q / Yi these networks. Evolved MTC (eMTC) is another term used for LTE-M. LTE-M can be described as a simplified version of LTE. For example, an LTE-M UE is less complex, has lower power consumption, and extended coverage compared to an LTE device. A UE can also be called a device. LTE-M can support a wide range of applications that require low data rates. It can be used for sensor monitoring in, for example, smart meters, tracking devices, etc. It can also support IoT applications that require real-time communications, such as voice, emergency data, etc., as well as those that require both fixed and mobile communications. Example use cases include wearable devices, patient monitoring, home security, industrial asset management, retail and POS, and transportation. Narrowband IoT (NB-IoT) is another LPWA technology applicable to IoT UEs. NB-IoT may also be referred to as Category M2, Category LTE NB1, or LTE-M2. UE category information can be used to enable a base station to communicate effectively with all connected UEs. The UE category defines, for example, whether the UE has a combined uplink and downlink capability. The term "class" can be used in... PLnfr / n / Lznz / q / Yi category place. In LTE, an LTE UE category indicates the uplink and / or downlink speed that the radio unit can handle. The LTE category can also indicate the number of antennas, i.e., the MIMO (Multiple Input Multiple Output) layer. LTE category MI has 1 Mbit / s downlink, 1 Mbit / s uplink, and one MIMO layer. LTE category M2 has 4 Mbit / s downlink, 6 Mbit / s uplink, and one MIMO layer. Working Group 2 (SA2) on Service and System Aspects of the Third Generation Partnership Project (3GPP) introduced a new type of Radio Access Technology (RAT) for LTE-M in order to apply an independent billing model to traffic from an LTE-M UE and introduce identification and transparency requirements in roaming. To meet these requirements, the Mobility Management Entity (MME) must indicate whether the UE is category M1 / M2 to the Service Gateway / Packet Unit Gateway (S-GW / P-GW) as a new RAT type in a Create Session Request message. The MME also needs to block incoming roaming for category M1 / M2 UEs on the initial connection if required by the carrier. Category M1 / M2 indicates that the UE is either category MI or category M2. Sometimes, the term category M is used. PLnfr / n / Lznz / q / Yi when referring to category MI or category M2, where M indicates MTC. Route Cat-M UEs to the specific dedicated core network (DCN) based on their initial connection request message or a trace area update request (TAU) message may also be required. During the initial connection procedure, the UE performs a random access, and the first message from the evolved Node B (eNB) to the core network (CN) is an INITIAL UE MESSAGE. At this stage, the eNB has no UE capacity information. The MME instructs the eNB to query the UE capacity in the Initial Context Establishment Request. The MME stores the UE capacity information until the UE disconnects. But with the current solution in 3GPP, which uses the M1 / M2 category to allocate the new LTE-M RAT type in the core network, the MME can only obtain an explicit LTE-M indication in the UE CAPACITY INFORMATION INDICATION, as shown in Figure 1 and Figure 2. Figure 1 shows that the eNB 103 provides the MME 105 with a UE capability information indication message in step 1). The UE capability information indication message comprises UE capability information, possibly in addition to other information. The UE capability information indicates the UE's radio capabilities. PLnfr / n / Lznz / q / Yi UE capacity information can include UE radio capacity information and UE core network capacity information. UE radio capacity information can include information about the RATs the UE supports, such as power class, frequency bands, etc. UE core network capacity can be divided into the UE network capacity information element (IE) and the mobile station network capacity (MS) IE, and includes non-radio-related capabilities, such as non-accessible layer security algorithms (NAS), etc. The eNB 103 determines if a UE is Category M based on the UE's radio capability and whether the UE indicates one or more of the specific Category M. The eNB 103 then indicates to the MME 105 whether the UE is Category M in the UE's radio capability for Category M differentiation information in an SI Application Protocol (SL-AP) message(s) used to load the UE's radio capabilities into the MME 105. Figure 2 comprises at least one of the following steps, which may be carried out in any order other than that described below: Step 201 MME 105 can send a request message to eNB 103. The request message can be a SLAP message, which can be an Initial Context Establishment Request. The message may include security capabilities. UE PLnfr / n / Lznz / q / Yi and UE radio capacity. The UE radio capacity may be in the form of UERadioAccessCapabilityInformation. Step 202 The eNB 103 can provide a response message to the MME 105. The response message can be a reply to the request message in step 201. The response message can be an SL-AP message. The response message can be an INITIAL CONTEXT CONFIGURATION RESPONSE. Step 203 The eNB 103 decides whether more capabilities are needed, for example, based on - what other RATs does UE 101 support, and / or - if such neighboring cells are present. Step 204 The eNB 103 can provide a Radio Resource Control (RRC) message to the UE 101. The RRC message can be a UEC capacity query message. The RRC message can indicate a RAT type. Step 205 UE 101 can provide an RRC response message to eNB 103. The RRC response message can contain UECapabilityInformation. The UECapabilityInformation can be, for example, a RAT container and / or UE-CapabilityRAT. Step 206 The eNB 103 maintains capabilities during the state PLnfr / n / Lznz / q / Yi RRC CONNECTED and creates a message UERadioAccessCapabilityInformation comprising at least substantially all known capabilities excluding the terrestrial radio access network (UTRAN) capability of the Universal Mobile Telecommunications System (UMTS). Step 207 The eNB 103 sends an SL-AP message to the MME 105. The SL-AP message can be a UE CAPACITY INFORMATION INDICATION message. The message can include the UE's radio capability. UERadioAccessCapabilitylnformation. Step 208 The MME 105 maintains capabilities until DISCONNECTION or CONNECTION. If MME 105 obtains the LTE-M indication IE in the UE CAPACITY INFORMATION INDICATION message, MME 105 will report the LTE-M RAT type to the S-GW and P-GW as shown in Figure 3. Figure 3 comprises at least one of the following steps, which may be carried out in any order other than that described below: Step 301 UE 101 can send a complete RRC connection establishment message to eNB 103. The message may contain or may be a Connect Request. Step 302 I / U / 4U I or The eNB 103 can send an initial UE message to the MME 105. Step 303 Authentication and security procedures are executed on the network. Step 304 MME 105 can send a location update request message to HSS 106. Step 305 The HSS 106 can send a location update response message to the MME 105. Step 306 MME 105 can send a session creation request message to GW 108. GW 108 can be an SGW or a PGW, etc. The session creation request message can include an LTE-M RAT indication. Step 307 GW 108 can send a Create session response message to MME 105. Step 308 MME 105 can send an Initial Context Establishment Request message to eNB 103. The message may include an indication of acceptance to connect. Step 309 The eNB 103 can send a query message of PLnfr / n / Lznz / q / Yii capacity of the UE to UE 101. Step 310 The UE 101 can send a UE capacity information indication message to the eNB 103. The message may include an LTE-M indication. Step 311 The eNB 103 can send an RRC connection reconfiguration message to the UE 101. Step 312 UE 101 can send a full RRC connection reconfiguration message to eNB 103. Step 313 The eNB 103 can send an initial context configuration response message to the MME 105. In the assembly procedure as shown in Figure 3, when MME 105 receives the initial UE message, it will send the session creation request to the SGW and indicate to SGW 108 that this is for an LTE-M1 / M2 UE for the charge. However, the UE capacity, if not available on MME 105, can be received from eNB 103 after the initial context configuration request / response (ICSR), which would arrive late. For block roaming of an M1 / M2 category UE, this would mean that UE 101 will always be accepted for the connection procedure and when MME 105 receives PLnfr / n / Lznz / q / Yi The UE's capacity after ICSR, the UE 101 can be detached. This means that the M roaming category UE can access the network for communication during the initial connection even though it should be blocked. It would also require extra signaling if access is allowed and disconnection is delayed, to block services. For Dedicated Network Center (DCN) selection, M1 / M2 category UEs may be routed to an incorrect DCN in the attachment. The UE Usage Type (UUT) setting is now per International Mobile Subscriber Identity (IMSI) level; however, if a Mobile Broadband (MBB) Universal Subscriber Identity Module (USIM) is inserted into an M1 / M2 category UE, after MME 105 in the incorrect DCN receives the UE's capabilities, a redirection may be required to direct UE 101 to the correct DCN. This requires additional network signaling, and the redirection may not occur immediately. In current technology, the CN receives the indication for LTE-M1 / M2 category UE in the UE capacity information after the UE context and user plane have been configured. This is too late. Therefore, there is a need to at least mitigate or resolve this problem. PLnfr / n / Lznz / q / Yi BRIEF DESCRIPTION OF THE INVENTION Therefore, one objective of the modalities described in this document is to avoid at least one of the aforementioned disadvantages and to provide improved information handling, for example, EU category information. In other words, to provide improved identification of an EU of a given category, for example, a first or second category. According to the first aspect, the objective is achieved through a method carried out by a first network node. The first network node determines which UE category a UE belongs to. The UE category is M or Low Complexity (BL) without reduced bandwidth in Coverage Enhancement (CE). The first network node provides UE category information about the determined UE category to a second network node. According to a second aspect, the objective is achieved through a first network node. The first network node is adapted to determine which UE category a UE belongs to. The UE category is M or non-BL in CE. The first network node is adapted to provide UE category information about the determined UE category to a second network node. According to a third aspect, the object is achieved through a method carried out by a second network node. The second network node obtains, from the first network node, PLnfr / n / Lznz / q / Yi UE category information about which UE category a UE belongs to. The UE category is M or non-BL in CE. The second network node provides the UE category information to a third network node. According to a fourth aspect, the objective is achieved through a second network node. The second network node is adapted to obtain UE category information from the first network node, specifying the UE category to which a given UE belongs. The UE category is M or non-BL in CE. The second network node is then adapted to provide this UE category information to a third network node. According to a fifth aspect, the objective is achieved through a method carried out by a UE. The UE provides an indication of the UE category to a first network node. The UE category is M or non-BL in CE. According to a sixth aspect, the objective is achieved through a UE. The UE is adapted to provide an indication of the UE category to a first network node. The UE category is M or non-BL in CE. The options in this document offer many advantages, of which the following is a non-exhaustive list of examples: • Reduce signage. • Provide information to the second network node, for example, the MME, in a timely manner. PLnfr / n / Lznz / q / Yi • Improve the decision base at the second node of the network, for example, the MME. • Reduce network signaling. • Reduce or avoid the need for a route change. • Direct the UE to the correct DCN. • The time to provide UE capacity information to the necessary nodes is improved. Another advantage of the methods in this document is that they correctly transfer the LTE-M RAT type to the SGW and PGW already in the context creation phase for loading. Another advantage of the methods described in this document is that they could block a Category M roaming UE when received in the initial UE message. Another advantage is that DCN selection is optimized based on the Category M capability of the UUT and UE. An additional advantage of the modalities in this document is that the charging and roaming policy can be applied according to the operator's wishes for normal UEs using CE. The features and benefits described in this document are not limited to those mentioned above. A person skilled in the art will recognize additional features and benefits upon reading the following detailed description. PLnfr / n / Lznz / q / Yi BRIEF DESCRIPTION OF THE DRAWINGS PLnfr / n / Lznz / q / Yi The modalities of this document will now be described in more detail by way of example only in the following detailed description with reference to the accompanying drawings that illustrate the modalities and in which: Figure 1 is a signaling diagram illustrating a method. Figure 2 is a signaling diagram illustrating a method. Figure 3 is a signaling diagram illustrating a method. Figure 4A is a schematic drawing illustrating a communications system. Figure 4B is a signaling diagram illustrating a method. Figure 5 is a signaling diagram illustrating a method. Figure 6A is a schematic drawing illustrating an example of a UE. Figure 6B is a schematic drawing illustrating an example of a UE. Figure 7A is a schematic drawing illustrating an example of a first network node. Figure 7B is a schematic drawing illustrating an example of a first network node. Figure 8A is a schematic drawing illustrating an example of a second network node. Figure 8B is a schematic drawing illustrating an example of a second network node. Figure 9 is a schematic block diagram illustrating a telecommunications network connected through an intermediate network to a main computer. Figure 10 is a schematic block diagram of a main computer communicating via a base station with a UE through a partially wireless connection. Figure 11 is a flowchart depicting modes of a method in a communications system that includes a main computer, a base station, and a UE. Figure 12 is a flowchart depicting modes of a method in a communications system that includes a main computer, a base station, and a UE. Figure 13 is a flowchart depicting modes of a method in a communications system that includes a main computer, a base station, and a UE. Figure 14 is a flowchart depicting modes of a method in a communications system that includes a main computer, a base station, and a UE. The drawings are not necessarily to scale and the dimensions of certain features may have been altered. PLnfr / n / Lznz / q / Yi exaggerated for the sake of clarity. Instead, emphasis is placed on illustrating the principle of the modalities of this document. DETAILED DESCRIPTION OF THE INVENTION Figure 4A illustrates non-limiting examples of a communications system 100, which may be a wireless communications network, sometimes also called a wireless communications system, cellular radio system, or cellular network, in which the modalities described in this document may be implemented. The communications system 100 may typically be a 5G system, a 5G network, a new or next-generation license-assisted access (LAA) radio system or network, MulteFire, a 4G system, a 3G system, a 2G system, an LTE-M system, a next-generation system, or any other suitable system. Alternatively, the communications system 100 may be a system that is newer than a 5G system.The 100 communications system may support other technologies such as, for example, Long-Term Evolution (LTE), LTE-M, LTE-Advanced / LTE-Advanced Pro, for example, LTE frequency-division duplex (FDD), LTE time-division duplex (TDD), LTE half-duplex frequency-division duplex (HD-FDD), LTE operating in an unlicensed band, and NB-IoT. Therefore, although 5G / NR and LTE terminology may be used in this description to exemplify the modalities herein, this should not be taken as an absolute requirement. PLnfr / n / Lznz / q / Yi should not be seen as limiting the scope of the modalities herein to only the systems mentioned above. The modalities of this document apply to any past, present, or future system. The communications system 100 comprises a plurality of network nodes, of which a first network node 103, a second network node 105, and a third network node 108, also referred to herein as network nodes 103, 105, 108, are represented in the non-limiting example of Figure 4A. Any of the first network node 103, the second network node 105, and the third network node 108 may be a radio network node, such as a base station, or any other network node with similar characteristics capable of serving a UE 101, such as a wireless device or a machine-type communication device, in the communications system 100. The base station may be a gNB, eNB, Nb, MeNB, etc.Any of the first network node 103, the second network node 105, and the third network node 108 can be a core network node such as an MME, General Packet Radio Service Support (GPRS) node, SGSN, PGW, SGW, User Plane Function (UPE), Access and Mobility Management (AME) function, etc. In some examples, either the first network node 103 and the second network node 105 can be co-located or part of the same network node. For example, the first network node 103. PLnfr / n / Lznz / q / Yi can be a base station such as an NB, eNB, gNB, master eNB (MeNB), home eNodeB (HeNB), radio network controller (RNC), etc. The second network node 105 can be, for example, a first core network node such as a mobility node, MME, SGSN, AMF, session management function (SMF), etc. The third network node 108 can be, for example, a second core network node such as a gateway (GW), PGW, SGW, UPF, etc. The communications system 100 covers a geographic area that can be divided into cell areas, where each cell area can be served by a network node, although a network node can serve one or more cells. In the example in Figure 4A, the communications system 100 can comprise a first cell (not shown). In Figure 4A, the first network node 103 can serve the first cell. Any of the first network node 103, the second network node 105, and the third network node 108, when they are base stations, can be of different classes, such as, for example, a macro base station, a home base station, or a pico base station, depending on the transmission power and, therefore, also on the cell size. Any of the first network node 103, the second network node 105, and the third network node 108 can be directly connected to one or more core networks.In some examples, any of the first network node 103, the second network node 105, and the third network node. PLnfr / n / Lznz / q / Yi 108 can be a distributed node, such as a virtual node in the cloud, and can perform its functions completely in the cloud, or partially, in collaboration with a node in the radio network. A plurality of UEs may be located in the communication system 100, of which one UE 101, which may also be referred to simply as a device, is represented in the non-limiting example in Figure 4A. UE 101, for example, an LTE UE or a 5G / NR UE, an IoT UE, an MTC UE, a BL-CE UE, a standard UE, a CE UE, a BL UE, or a non-BL CE UE, may be a wireless communication device that may also be known as, for example, a wireless device, a mobile terminal, a wireless terminal and / or a mobile station, a mobile phone, a cell phone, or a wireless-enabled laptop, to mention just a few additional examples. UE 101 may be a device through which a subscriber can access services offered by an operator's network and services outside the operator's network to which the operator's radio access network and core network provide access, for example, internet access.The UE 101 can be any device, mobile or stationary, enabled to communicate via a radio channel on the communications network, for example, but not limited to, for example, user equipment, mobile phone, smartphone. PLnfr / n / Lznz / q / Yi sensors, meters, vehicles, household appliances, medical devices, media players, cameras, machine-to-machine (M2M) devices, IoT devices, terminal devices, communication devices, or any type of consumer electronics, for example, but not limited to televisions, radios, lighting arrangements, tablets, laptops, or personal computers (PCs).The UE 101 can be a portable, pocket-sized, handheld, computer-based, or vehicle-mounted device enabled to communicate voice and / or data, via the radio access network, with another entity, such as another UE, a server, a laptop computer, a personal digital assistant (PDA), or a tablet, an M2M device, a device equipped with a wireless interface, such as a printer or file storage device, a modem, or any other radio network unit capable of communicating via a radio link in a 100 communications system. The first network node 103 can be configured to communicate within the communication system 100 with UE 101 via a first communication link, for example, a radio link. The second network node 105 can be configured to communicate within the communication system 100 with the first network node 103 via a second communication link, for example, a radio link. The third network node 108 can be configured to communicate within the system PLnfr / n / Lznz / q / Yi of communications 100 with the second network node 105 through a third communication link, for example a radio link or a cable link, although communication through more links may be possible. The UE 101 is enabled to communicate wirelessly within the 100 communications system. Communication can be carried out, for example, between two devices, between a device and a regular telephone, between the UE 101 and a network node, between network nodes and / or between devices and a server via the radio access network and possibly one or more core networks and possibly the Internet. It should be noted that communication links in the communications network can be of any suitable type, including wired or wireless links. The link can use any appropriate protocol depending on the type and layer level (e.g., as indicated by the OSI model), as will be understood by someone skilled in the field. Figure 4B is a signaling diagram illustrating one method. The first network node shown in Figure 4B can be an access node, for example, an eNB, gNB, NB, base station, or RNC. UE 101 can be an IoT UE, an IoT device, an MTC device, or an MTC UE. The second network node 105 can be a mobility node, an MME, an SGSN, a combined MME / SGSN node, an AME, or a PLnfr / n / Lznz / q / Yi SMF, etc. The method comprises at least one of the following steps, which can be carried out in any order other than that described below: Step 401 This step may correspond to step 506 in Figure 5. UE 101 can send an indication of the UE category to the first network node 103. The first network node 103 can receive the UE category indication from UE 101. This step can be described as UE 101 providing the UE category indication to the first network node 103, and the first network node 103 receiving the UE category indication from UE 101. The indication specifies the UE 101's capability, for example, the category to which the UE 101 belongs. UE category information may be UE radio category information. UE category information may be referred to as UE capability information, or UE category information may be included within UE capability information. The indication can be sent by UE 101 to the first network node 103 in an RRC message, for example, an RRCConnectionSetupComplete message. Prior to step 401, UE 101 may have determined what type of radio resources it will use and disseminated information PLnfr / n / Lznz / q / Yi on this, for example, via SIB2. Instead of UE 101 sending the indication to the first network node 103, the first network node 103 can detect the UE category from information, for example, a preamble, received in a random access procedure, for example, broadcast information. Therefore, with the broadcast information, the first network node 103 can be aware, for example, by detecting a preamble during a random access procedure, that UE 101 is category MI, category M2, or a non-BL UE in CE. Step 402 The second network node 105 determines that it wants to know the UE category information. Step 403 This step corresponds to step 504 in Figure 5. The second network node 105 can send an indication to the first network node 103 that it wants to know the UE category information. The first network node 103 can receive the indication from the second network node 105. The second network node 105 can send, for example, during an SI configuration procedure, an indication that it wants to know the UE category information. Step 404 The first network node 103 determines which UE category UE 101 belongs to. The UE category can be category PLnfr / n / Lznz / q / Yi M or not BL in CE. Category M can be category MI or category M2. When the UE 101 belongs to category M, then the UE 101 can be described as a category M UE or a BL UE. When UE 101 is not in category M, then UE 101 can be described as a non-BL UE in CE, or a UE that belongs to a category other than category M, i.e., different from category MI and category M2. A category other than category M could be, for example, category 1, category 2, category 3, or category n, where n is a positive integer. The second category could be called the normal category or any other category except MI and M2. The first and second categories are distinct from each other. Step 404 can be performed before steps 402-403, after steps 402-403, between steps 402 and 403, or at the same time as steps 402-403. Determining EU category may involve detecting EU category in a random access procedure. The UE category can be determined based on the indication in step 401, for example, in an RRC message such as a complete RRC connection configuration message. The UE category can be determined based on PLnfr / n / Lznz / q / Yi information from the random access procedure, for example, by detecting the preamble during the random access procedure. When a Category M UE 101 has been previously deployed in the communications system 100, the indication in step 401 indicates a UE that is not BL in CE, and when the information in the random access procedure, for example, the preamble, does not comprise any indication for a UE that is not BL in CE, then the first network node 103 can determine that the UE 101 belongs to Category M. Step 405 This step corresponds to steps 502 and 508 in Figure 5. The first network node, 103, sends the UE category information to the second network node, 105. The second network node, 105, receives the UE category information from the first network node, 103. This step can be described as the first network node, 103, providing the determined UE category information to the second network node, 105. The UE category is either M1 / M2 or non-BL in CE. The UE category information may be referred to as UE capacity information, or the UE category information may be contained within the UE capacity information. The first network node 103 can send the UE category information to the second network node 105 before the PLnfr / n / Lznz / q / Yi second network node 105 create the session to the service GW, or choose the DCN. UE category information can be sent to the second network node 105 in, for example, an initial UE message. This UE category information can be sent to the second network node 105 before it establishes a session with the gateway. Step 406 The second network node 103 can send UE category information to the third network node 108. The third network node 108 can receive UE category information from the second network node 105. This step can be described as the second network node 105 providing UE category information to the third network node 108. The third network node 108 could be, for example, a GW. Step 407 The second network node 105 can determine whether to treat UEs 101 of all UE categories the same or differently in relation to at least one charge and roaming. When the second network node 105 has determined that it should treat UEs 101 of a certain category differently from UEs 101 of other categories, then the second network node 105 can request UE capacity information from the first network node 103 for UE 101. PLnfr / n / Lznz / q / Yi Step 407 can be performed after step 406 or after step 406. Step 407 can be performed after step 402 and before step 403. Step 408 The second network node 105 can obtain UE capacity information from UE 101 through the first network node 103. For example, the second network node 105 can, according to local policy, send the downlink ÑAS transport with an explicit indication of requesting UE radio capacity to the first network node 103. Then, the first network node 103 can obtain UE radio capacity from UE 101. If the second network node 105 wants special treatment only for Category M UEs, it can request the first network node 103 to obtain the UE's radio capacity. For example, it sends the UE radio capacity matching request to the first network node 103 to obtain the UE radio capacity of UE 101. Step 409 The second network node 105 can use UE category information. The second network node 105 can use UE category information based on a decision result in step 407. The second network node 105 can use UE category information to apply DCN loading or PLnfr / n / Lznz / q / Yii a roaming policy. Figure 5 is a signaling diagram illustrating an example method for indicating BL-CE UEs to MME 105, after eNB 103 has detected UE 101 in a Random Access Channel (RACH) procedure. Figure 5 illustrates the same method as Figure 4B, but provides more detail. In Figure 5, the first network node 103 is represented by an eNB 103, the second network node 105 by an MME 105, and the third network node 108 by a GW 108. However, the first, second, and third network nodes 103, 105, and 108 can be any other suitable nodes, such as those described earlier with reference to Figure 4A. The method comprises at least one of the following steps, which can be carried out in any order other than that described below: Step 501 This step corresponds to step 301 in Figure 3. UE 101 can send a complete RRC connection establishment message to eNB 103. The message may contain or may be a connection request. Step 502 The eNB 103 can send an initial UE message to the MME 105. The message includes a BL-CE indication, meaning that the UE 101 is a BL-CE UE. See the PLnfr / n / Lznz / q / Yii Table 1 provides an example of the initial UE message. Step 503 This step corresponds to step 303 in figure 3. The authentication and security procedures are executed on the communications system 100. Step 504 MME 105 can send a downlink UE / NAS transport radio capacity matching request to eNB 103. The UE radio capacity matching request may be called a UE category matching request. Step 505 This step corresponds to step 309 in Figure 3. The eNB 103 can send a UE capacity query message to the UE 101. The UE capacity query message may be called a UE category query message. Step 506 UE 101 can send UE capability information to eNB 103. This step can be described as UE 101 being able to send UE category information to eNB 103, and the UE category information may be contained within the UE capability information. Step 507 The eNB 103 can send a UE radio capability match response to the MME 105. The response from PLnfr / n / Lznz / q / Yi UE radio capability match can be called UE category match response. Step 508 The eNB 103 can send an EU capacity information indication to the MME 105. The EU capacity information indication may be called an EU category information indication or an EU category indication. Step 509 This step corresponds to step 304 in Figure 3. MME 105 can send a location update request message to HSS 106. Step 510 This step corresponds to step 305 in Figure 3. The HSS 106 can send a location update response message to the MME 105. Step 511 MME 105 can send a session creation request message to GW 108. Step 512 GW 108 can send a Create session response to MME 105. Step 513 This step corresponds to step 308 in Figure 3. MME 105 can send an initial context establishment request message to eNB 103. The message can include PLnfr / n / Lznz / q / Yii an indication to accept connection. Step 514 This step corresponds to step 311 in Figure 3. The eNB 103 can send an RRC connection reconfiguration message to the UE 101. Step 515 This step corresponds to step 312 in Figure 3. UE 101 can send a full RRC connection reconfiguration message to eNB 103. Step 516 This step corresponds to step 313 in Figure 3. The eNB 103 can send an initial context configuration response message to the MME 105. Before a UE 101 sends an Msgl, for example, a RACH preamble, it has to determine what type of RACH resource to use. This information is transmitted through system information block 2 (SIB2). If UE 101 is a BL UE or a UE in EC, then eNB 103 would detect this during the random access procedure. Therefore, at least by detecting the preamble, eNB 103 would know that UE 101 is a BL UE, i.e., category MI or category M2, or a UE 101 in CE, i.e., a standard category UE that supports CE. The following modalities 1 and 2 can be seen as EU-based solutions: PLnfr / n / Lznz / q / Yi Option 1: • Step the: This step corresponds to step 401 in figure 4B. Or, an indication can be entered in an RRC message, for example, the message RRCConnectionSetupComplete, to inform eNB 103 whether UE 101 is an M1 / M2 category UE, i.e., category M, or a normal category UE using CE, i.e., a non-BL UE in CE. • Step 2a: This step 2a corresponds to steps 404 and 405 in figure 4B. Or the eNB 103 can then include the LTE-M indication in the initial UE message. Option 2: Given that M1 / M2 category UEs have already been implemented, as they are included in the early versions of RRC, this is not the case for standard category UEs that support CE, as these will appear in a later version. Therefore, another possible solution is the following: • Step Ib: O This step Ib corresponds to step 401 of Figure 4B. PLnfr / n / Lznz / q / Yi Or have a mandatory indication in the message RRC, for example, RRCConnectionSetupComplete message, to indicate that UE 101 is a normal category UE using CE, i.e., a non-BL UE in CE. • Step 2b: This step 2b corresponds to step 401 and step 404 of figure 4B. The eNB 103 detects the preambles used by the UE 101. If there is no explicit indication for a non-BL UE in the CE, since it is mandatory for such a UE 101, then the eNB 103 could conclude that the UE 101 is of category M1 / M2. This makes the solution relatively easy to implement early on. • Step 3b: This step 3b corresponds to step 405 in figure 4B. Or the eNB 103 may include the LTE-M indication in the initial UE message, i.e., the indication of category M. This indication in step Ib of mode 2 can be provided in a legacy message, namely RRCConnectionSetupComplete, which has been used since the early versions of 3GPP. The field parameter is a new addition. A field parameter is added for a UE 101 to indicate whether it is Category M1 / M2 Version 13 (Rel-13); otherwise, one would not be able to route those UE 101s to the correct DCN during PLnfr / n / Lznz / q / Yi is the initial connection procedure. This field parameter would be optional when coded in Abstract Syntax Notation 1 (ASN.1) since there is no need for a legacy, i.e., normal category UE, to signal it. An alternative is to introduce a field parameter indicating whether UE 101 is a non-BL UE in CE. For the same reason as above, this should be implemented from Rel-13 onwards, but the field parameter will again be optional with a condition such as the field is required if the UE is a non-BL UE in CE, or something similar. Options 3, 4, and 5 can be viewed as a network-based solution, as shown in Figures 4B and 5: Option 3: • Step 1c: This step 1c corresponds to step 401 in figure 4B. The eNB 103 detects that M1 / M2 category UE or a non-BL UE in CE in a random access procedure. • Step 2c: Based on local policy, eNB 103 activates the UEC capacity query procedure to obtain UE radio capacity from UE 101. • Step 3c: This step 3c corresponds to step 405 in figure 4B. PLnfr / n / Lznz / q / Yi The eNB 103 includes a category indication M, for example, an LTE-M indication in the initial UE message. Alternatively, MME 105 could indicate to eNB 103 during the SI configuration procedure that it is interested in knowing whether UE 101 is an LTE-M device (see step 402 and step 403 in figure 4B), or whether UE 101 is an LTE-M and the normal UE that uses CE, so eNB 103 could act accordingly. Option 4: • Step Id: This step Id corresponds to step 401 of figure 4B. The eNB 103 detects BL and / or CE UEs or normal UEs that use CE in random access, i.e., it detects category M UEs or non-BL UEs in CE; • Step 2d: This step 2d corresponds to step 405 in figure 4B. Or the eNB 103 indicates to the MME 105, for example, in an INITIAL UE MESSAGE that the UE 101 is BL-CE, which means that the UE 101 is BL and / or CE or normal UE that uses CE, see figure 3. • Step 3d: This 3D step corresponds to step 407 of the PLnfr / n / Lznz / q / Yi figure 4B. Or MME 105, based on local policy, decides whether to treat all UE BL and / or CE, or normal UE using CE, in the same way, when it relates to collection, roaming. • Step 4d: This step 4d corresponds to step 408 in figure 4B. Or, if MME 105 wants to handle only the LTE-M UEs, it will request the eNB 103 to obtain the UE radio capacity. For example, it sends the UE radio capacity match request to eNB 103 to obtain the UE radio capacity from UE 101. After MME 103 has received the UE CAPACITY INFORMATION INDICATION, it includes the LTE-M indication to proceed with the next procedure, such as establishing a session to the SGW, configuring the initial context, and setting up the user plane to the RAN. Modalities 5: • Step le and step 3e are the same as in mode 3, that is, the same as steps Id and 3d. • Step 4e: O This step 4e corresponds to step 408 of Figure 4B. Or, in accordance with local policy, MME 105 sends the downlink ÑAS transport with indication PLnfr / n / Lznz / q / Yi explicit request for UE radio capacity to eNB 103. Then, eNB 103 obtains UE radio capacity from UE 101, after MME 105 received the UE CAPACITY INFORMATION INDICATION, include the LTE-M indication to continue with the following procedure. For the network-based solution, it is assumed that for most UE 101s, it is not necessary to obtain the UE category during the UE connection procedure. Only when the eNB 103 detects that special preambles are being used, i.e., that UE 101 is a BL / CE, or a normal UE using CE, may it be necessary to obtain the radio capability of the UE so that MME 105 can use the information to apply the DCN, payload, or roaming policy. Note that the solution steps do not need to be applied in order in some cases, for example, in mode 2. Note that the eNB 103 could exclude NB-IoT UEs using message (msg) 5 information, the RRC connection configuration. If it cannot, the same procedures described above would apply. Note that the modalities apply to NR, when the MI category, the M2 category or the normal EU category using CE or in CE will be admitted. The communications system 100 can be a system PLnfr / n / Lznz / q / Yi 5G, a 4G system, a 3G system, or a 2G system, or any PLnfr / n / Lznz / q / Yii future system. INITIAL EU MESSAGE This message is sent by the first network node 103 to transfer the initial Layer 3 message to the second network node 105 via the SI interface, for example, as seen in step 502 in Figure 5. An example of the initial UE message is shown in Table 1 below. The initial UE message is transmitted in the direction from the first network node 103 to the second network node 105. Table 1 - Initial EU Message lE / Group Name Presence Rank Type of lEy reference Semantic description Criticality Assigned criticality Message type M 9.2.1.1 Yes ignore eNB UES1AP ID M 9.2.3.4 Yes reject r NAS-PDU M 9.2.3.5 Yes reject r TAI M 9.2.3.16 Indicates the Tracking Area from which the UE sent the NAS message. Yes reject r E-UTRAN CGI M 9.2.1.38 Indicates the EUTRAN CGI from which the UE sent the ÑAS message. If ignore RRC Establishment Cause M 9.2.1.3a If ignore S-TMSI 0 9.2.3.6 Yes reject r CSG ID 0 9.2.1.62 Yes reject r GUMMEI 0 9.2.3.9 Yes reject r Cellular Access Mode 0 9.2.1.74 Yes reject r GW Transport Layer Address 0 Transport Layer Address 9.2.2.1 Indicates the GW transport layer address if the GW is placed with eNB. Yes ignore Relay Node Flag 0 9.2.1.79 Indicates a relay node. Yes reject r GUMMEI Type 0 ENUMER ADO (native, mapped, ...) Yes ignore r ιηπ / η / ιzoz / zi / yl Tunnel Information for BBF 0 Tunnel Information 9.2.2.3 Indicates the HeNB's local IP address assigned by the Broadband Access Provider, UDP port number. If Ignore Transport Layer Address SIPTO L-GW 0 Transport Layer Address 9.2.2.1 Indicates the SIPTO L-GW transport layer address if the SIPTO L-GW is co-located with eNB. If Ignore LHN ID 0 9.2.1.92 If Ignore MME Group ID 0 9.2.3.44 If Ignore UE Usage Type 0 INTEGER (0..255) If Ignore CE-modeB Support Indicator 0 9.2.1.118 If Ignore DCN ID 0 INTEGER (0..65535) If Ignore Coverage Level 0 ENUMERATED (extended coverage,...) If Ignore r ι ηπ / η / ι znz / zi / Yl· UE Application Layer Measurement Capability 0 BIT STRING (SIZE 0(8)) Each bit in the bitmap indicates a UE application layer measurement capability, see TS 25.331

[10] . Bit 0 = QoE measurement for broadcast service. Bit 1 = QoE measurement for MTSI service. The value 1 indicates Capable and the value 0 indicates Not Capable. Unused bits are reserved for future use. If ignore, EDT Session 0 ENUMERATED (true,...) Yes IVIA / t / ZUZ I / U / 4U I or BL-CE 0 xyz Indication: This is indicated if the UE is BL-CE, or a normal UE that uses CE. If ignored, PLnfr / n / Lznz / q / Yii BL-CE Indication This IE is provided by the first network node 103 to report that the EU is a Category M EU or a non-EU BL in CE, for example, a BL and / or CE, or a standard EU that uses CE. The BL-CE designation may also be called EU category information or EU category indication. EU category information may be included within EU capacity information. The BL-CE designation can be seen in Table 2 below. Table 2 - BL-CE Indication IE / Group Name Presence Range IE Type and Reference Semantic Description BL-CE Indication M ENUMERADO (BL-CE, ...) The BL-CE value indicates that the UE is BL and / or CE, or a normal UE that uses CE. A computer program may comprise instructions that, when executed on at least one processor, cause the processor to carry out the method in accordance with any one of the modalities herein. A carrier may comprise the computer program, wherein the carrier is an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. Figure 6A and Figure 6B represent two different examples in panels a) and b), respectively, of the arrangement that UE 101 may comprise. In some embodiments, UE 101 may comprise the following arrangement represented in Figure 6A. The modes described herein in the UE 101 can be implemented through one or more processors, such as a first processor 501 in the UE 101 depicted in Figure 6A, along with the computer program code to perform the functions and actions of the modes described herein. A processor, as used herein, can be understood as a hardware component. The program code mentioned above can also be provided as a computer program product, for example, in the form of a data carrier that carries computer program code to perform the modes described herein when loaded into the UE 101. One such carrier can be in the form of a CD-ROM. However, it is feasible with other data carriers such as a USB flash drive. Furthermore, the program code of PLnfr / n / Lznz / q / Yii computer can be provided as pure program code on a server and downloaded to UE 101. The UE 101 may further comprise a first memory 503 comprising one or more memory units. The first memory 503 is arranged to be used for storing acquired information, data, configurations, programs, and applications, etc., to carry out the methods described herein when executed on the UE 101. In some configurations, UE 101 can receive information from, for example, the first network node 103 and / or the second network node 105, via a first receive port 504. In some configurations, the first receive port 504 can be connected to one or more antennas on UE 101. In other configurations, UE 101 can receive information from another structure in the communications system 100 via the first receive port 504. Since the first receive port 504 can be in communication with the first processor 501, the first receive port 504 can send the received information to the first processor 501. The first receive port 504 can also be configured to receive other information. The first processor 501 in the UE 101 can also be configured to transmit or send information to, for example, the first network node 103 and / or the second network node 105 and / or the third network node 108, or another structure in the system PLnfr / n / Lznz / q / Yi of communications 100, through a first sending port 505, which can be in communication with the first processor 510, and the first memory 503. UE 101 may comprise a determination unit 515, a obtaining unit 518, a provision unit 528, other unit(s) 530, etc. The UE 101 can be adapted, for example, by means of the provisioning unit 528, to provide an indication of the UE category to the first network node 103. The indication specifies the category to which the UE belongs. The UE 101 can also be adapted, for example, by means of the retrieval unit 518, to receive an indication request from the first network node. Those skilled in the art will also appreciate that the determination unit 515, the acquisition unit 518, a provisioning unit 528, and other units 530 described above may refer to a combination of analog and digital circuitry and / or one or more processors configured with software and / or firmware, for example, stored in memory, which, when executed by one or more processors such as the first processor 501, function as described above. One or more of these processors, as well as the other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among PLnfr / n / Lznz / q / Yi several separate components, either individually packaged or assembled into a system on a chip (SoC). Furthermore, in some configurations, the different 515-530 units described above can be implemented as one or more applications running on one or more processors, such as the first 501 processor. Therefore, the methods according to the modalities described herein for UE 101 can be implemented respectively by means of a first computer program product 510, comprising instructions, i.e., portions of software code, which, when executed on at least one first processor 501, cause the at least one first processor 501 to perform the actions described herein, as performed by UE 101. The first computer program product 510 can be stored on a first computer-readable storage medium 508. The first computer-readable storage medium 508, which has the first computer program 510 stored thereon, can comprise instructions which, when executed on at least one first processor 501, cause the at least one first processor 501 to perform the actions described herein, as performed by UE 101.In some forms, the first computer-readable storage medium 508 may be a non-transient computer-readable storage medium, such as. PLnfr / n / Lznz / q / Yi as a CD-ROM disk or a memory stick. In other embodiments, the first computer program product 510 can be stored on a medium containing the first computer program 510 just described, wherein the medium is an electronic signal, an optical signal, a radio signal, or the first computer-readable storage medium 508, as described above. The UE 101 may comprise a communication interface configured to facilitate communication between the UE 101 and other nodes or devices, for example, the first network node 103 and / or the second network node 105 and / or the third network node 108, or other structure. The interface may include, for example, a transceiver configured to transmit and receive radio signals via an air interface in accordance with a suitable standard. In other embodiments, the UE 101 may comprise the following arrangement depicted in Figure 6B. The UE 101 may comprise a first processing circuit 511, for example, one or more processors such as the first processor 510, in the UE 101 and the first memory 503. The UE 101 may also comprise a first radio circuit 513, which may comprise, for example, the first receive port 504 and the first send port 505. The first processing circuit 511 may be configured to, or operable to, carry out the actions of the method in accordance with the PLnfr / n / Lznz / q / Yi figure 1-figure 5, similarly to that described in relation to figure 6A. The first radio circuit 513 can be configured to establish and maintain at least one wireless connection with the UE 101. Circuit can be understood here as a hardware component. Therefore, the modalities of this document also refer to UE 101 operational for operation in the communication system 100. UE 101 may comprise the first processing circuit 511 and the first memory 503. The first memory 503 comprises instructions executable by said first processing circuit 511. UE 101 is further operational for carrying out the actions described in this document in relation to UE 101, for example, in Figure 5. Figure 7A and Figure 7B represent two different examples in panels a) and b), respectively, of the arrangement that the first network node 103 may comprise. In some modalities, the first network node 105 may comprise the following arrangement represented in Figure 7A. The modalities of this document in the first network node 103 can be implemented through one or more processors, such as a second processor 601 in the first network node 103 represented in Figure 7A, together with computer program code to carry out the functions and PLnfr / n / Lznz / q / Yi actions of the modalities herein. A processor, as used herein, may be understood as a hardware component. The program code mentioned above may also be provided as a computer program product, for example, in the form of a data carrier that carries computer program code to carry out the modalities herein when loaded into the first network node 103. One such carrier may be in the form of a CD-ROM disk. However, it is feasible with other data carriers such as a memory stick. In addition, the computer program code may be provided as pure program code on a server and downloaded to the first network node 103. The first network node 103 may further comprise a second memory 603 comprising one or more memory units. The second memory 603 is arranged to be used for storing acquired information, data, configurations, programs, and applications, etc., to carry out the methods described herein when executed on the first network node 103. In some configurations, the first network node 103 can receive information from, for example, UE 101 and / or the second network node 105 and / or the third network node 108, through a second receive port 604. In some configurations, the second receive port 604 can be, for example, PLnfr / n / Lznz / q / Yi connected to one or more antennas on the first network node 103. In other modes, the first network node 103 can receive information from another structure in the communications system 100 through the second receive port 604. Since the second receive port 604 can be in communication with the second processor 601, the second receive port 604 can then send the received information to the second processor 601. The second receive port 604 can also be configured to receive other information. The second processor 601 in the first network node 103 can be further configured to transmit or send information to, for example, the UE 101 and / or the second network node 105, or another structure in the communications system 100, through a second forwarding port 605, which can be in communication with the second processor 601 and the second memory 603. The first network node 103 may comprise a determination unit 613, a creation unit 615, a provisioning unit 618, other unit(s) 620, etc. The first network node 103 is adapted, for example, by means of the determination unit 613, to determine which UE category a UE 101 belongs. The UE category is at least one of a first category and a second category. The first category may be MI or M2. The second category may be non-BL in CE. The first network node 103 is adapted, for example, PLnfr / n / Lznz / q / Yi through provisioning unit 618, provide UE category information on the determined UE category to a second network node 105. The first network node 130 can be adapted to, for example, by means of the determination unit 613, determine the UE category by detecting the UE category in a random access procedure. The first network node 103 can be adapted to, for example, by means of the determination unit 613, determine the UE category based on an indication received from UE 101. The indication received from UE 101 may indicate a second category, for example, a UE that is not BL in CE, and then the first network node 103 may detect that no explicit indication of a non-BL in CE category is included in a RACH preamble. Therefore, the first network node 103 may adapt itself to, for example, using determination unit 613, determine that UE 101 belongs to category M, for example, MI or M2. The first network node 103 can be adapted to, for example, by means of the second receive port 604, receive, from the second network node 105, an indication that the second network node 105 wishes to know the UE category information. When the first network node 103 detects that it is in use PLnfr / n / Lznz / q / Yi a special preamble, then it can be adapted to, for example, by means of determination unit 613, determine that EU category information needs to be obtained. EU category information may be included in EU capability information or may be EU capability information. The first network node 103 can be an access node, for example, an eNB, gNB, NB, base station, or RNC. The UE 101 can be an IoT UE, an IoT device, an MTC device, or an MTC UE. The second network node 105 can be a mobility node, an MME, an SGSN, a combined MME / SGSN node, an AME, an SMF, etc. Those skilled in the art will also appreciate that the determination unit 613, the creation unit 615, the provisioning unit 618, other units 620, etc., described above, may refer to a combination of analog and digital circuitry, and / or one or more processors configured with software and / or firmware, for example, stored in memory, which, when executed by one or more processors such as the second processor 601, operate as described above. One or more of these processors, as well as the other digital hardware, may be included in a single ASIC, or several processors and various digital hardware may be distributed among several separate components, either individually packaged or assembled. PLnfr / n / Lznz / q / Yi in a SoC. Furthermore, in some configurations, the different 613-620 units described above can be implemented as one or more applications running on one or more processors, such as the second 601 processor. Therefore, the methods according to the modalities described herein for the first network node 103 can be implemented respectively by means of a second computer program product 610, comprising instructions, i.e., parts of software code, which, when executed on at least a second processor 601, cause the at least a second processor 601 to perform the actions described herein, just as the first network node 103 performs them. The second computer program product 610 can be stored on a second computer-readable storage medium 608.The computer-readable storage medium 608, which has the second computer program 610 stored therein, may comprise instructions that, when executed on at least one second processor 601, cause the at least one second processor 601 to perform the actions described herein, as performed by network node 105. In some embodiments, the computer-readable storage medium 610 may be a non-transient computer-readable storage medium, such as a CD-ROM disk. PLnfr / n / Lznz / q / Yii or a memory stick. In other embodiments, the second computer program product 610 can be stored on a carrier containing the second computer program 610 just described, wherein the carrier is an electronic signal, an optical signal, a radio signal, or the second computer-readable storage medium 608, as described above. The first network node 103 may comprise a communication interface configured to facilitate communication between the first network node 103 and other nodes or devices, for example, UE 101 and / or the second network node 105 and / or the third network node 108, or other structure. The interface may include, for example, a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard. In other embodiments, the first network node 103 may comprise the arrangement shown in Figure 7B. The first network node 103 may comprise a second processing circuit 611, for example, one or more processors such as the second processor 601, in the first network node 103 and the second memory 603. The first network node 103 may also comprise a second radio circuit 613, which may comprise, for example, the second receive port 604 and the second send port 605. The second processing circuit 611 may be configured to PLnfr / n / Lznz / q / Yi carry out the actions of the method according to Figure 5 in a manner similar to that described in relation to Figure 7A. The second radio circuit 613 can be configured to establish and maintain at least one wireless connection with the first network node 103. Circuit can be understood here as a hardware component. Therefore, the modalities of this document also refer to the first network node 103 operational for operation in the communications system 100. The first network node 103 may comprise the second processing circuit 613 and the second memory 603. The second memory 603 contains instructions executable by said second processing circuit 613. The first network node 103 is further operational for carrying out the actions described in this document in relation to the first network node 103, for example, in Figure 5. Figure 8A and Figure 8B represent two different examples in panels a) and b), respectively, of the arrangement that the second network node 105 may comprise. In some embodiments, the second network node 105 may comprise the following arrangement represented in Figure 8A. The modalities in this document on the second network node 105 can be implemented through one or more processors, such as a third processor 701 in the The second network node 105, represented in Figure 8A, along with computer program code to carry out the functions and actions of the modalities described in this document, is represented as such. A processor, as used herein, may be understood as a hardware component. The aforementioned program code may also be provided as a computer program product, for example, in the form of a data carrier that carries computer program code to carry out the modalities described herein when loaded into the second network node 105. One such carrier may be in the form of a CD-ROM. However, it is feasible with other data carriers such as a USB flash drive. In addition, the computer program code may be provided as pure program code on a server and downloaded to the second network node 105. The second network node 105 may further comprise a third memory 703 comprising one or more memory units. The third memory 703 is intended to be used for storing acquired information, data, configurations, programs, and applications, etc., to carry out the methods in this document when executed on the second network node 105. In some configurations, the second network node 105 can receive information from, for example, UE 101 and / or the first network node 103 and / or the third network node 108, through PLnfr / n / Lznz / q / Yi from a third receive port 704. In some modes, the third receive port 704 may be, for example, connected to one or more antennas on the second network node 105. In other modes, the second network node 105 may receive information from another structure in the communications system 100 through the second receive port 604. Since the third receive port 704 may be in communication with the third processor 601, the third receive port 704 may then send the received information to the third processor 701. The third receive port 704 may also be configured to receive other information. The third processor 701 in the second network node 105 can be further configured to transmit or send information to, for example, the UE 101 and / or the first network node 103, and / or the third network node 108 or another structure in the communications system 100, through a third forwarding port 705, which can be in communication with the third processor 701 and the third memory 703. The second network node 105 may comprise a determination unit 713, a creation unit 715, a provisioning unit 718, other units 720, etc. The second network node 105 can be adapted to, for example, via the third receive port 704, obtain UE category information from the first network node 105 regarding which UE category a UE 101 belongs to. The category PLnfr / n / Lznz / q / Yi EU is category M or non-BL in CE. The second network node 105 can be adapted to, for example, by means of provisioning unit 718, provide UE category information to a third network node 108. The second network node 105 can be adapted to, for example, by means of the determination unit 713, determine that the second network node 105 wants to know the UE category information. The second network node 105 can be adapted to, for example, by means of the third sending port 705, transmit to the first network node 103 an indication that the second network node 105 wishes to know the UE category information. The second network node 105 can be adapted to, for example, by means of the determination unit 713, determine whether it wants to treat UEs 101 of all categories in the same or different ways related to at least one charge and roaming. When the second network node 105 has determined that it should treat UEs 101 of a certain category differently from UEs 10) of other categories, then the second network node 105 can adapt to, for example, by means of the third forwarding port 705, request UE category information from the first network node 103. The second network node 105 can be adapted to, for PLnfr / n / Lznz / q / Yi example, by means of the third processor 701, use the UE category information to apply the DCN roaming or charging policy. The first network node 103 can be an eNB, gNB, NB, base station, or RNC. The UE can be an IoT UE, an IoT device, an MTC device, or an MTC UE. The second network node 105 can be a mobility node, an MME, an SGSN, a combined MME / SGSN node, an AME, an SMF, etc. Those skilled in the art will also appreciate that the determination unit 713, the creation unit 715, the provisioning unit 718, other units 720, etc., described above, may refer to a combination of analog and digital circuitry, and / or one or more processors configured with software and / or firmware, for example, stored in memory, which, when executed by one or more processors, such as the third processor 701, operate as described above. One or more of these processors, as well as the other digital hardware, may be included in a single ASIC, or several processors and various digital hardware may be distributed among several separate components, either individually packaged or assembled into a SoC. Furthermore, in some configurations, the different 713-720 units described above can be implemented as one or more applications running on one or more PLnfr / n / Lznz / q / Yi processors, such as the third processor 701. Therefore, the methods according to the modalities described herein for the second network node 105 can be implemented respectively by means of a third computer program product 710, comprising instructions, i.e., parts of software code, which, when executed on at least a third processor 701, cause the at least a third processor 701 to perform the actions described herein, just as the second network node 105 performs them. The third computer program product 710 can be stored on a third computer-readable storage medium 708.The computer-readable storage medium 608, which contains the third computer program 710, may comprise instructions that, when executed on at least one third processor 701, cause that at least one third processor 701 to perform the actions described herein, as performed by the second network node 105. In some embodiments, the third computer-readable storage medium 710 may be a non-transient, computer-readable storage medium, such as a CD-ROM or a memory stick. In other embodiments, the third computer program product 710 may be stored on a carrier containing the third computer program 710 that was just created. PLnfr / n / Lznz / q / Yii describe, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or the third computer-readable storage medium 708, as described above. The second network node 105 may comprise a communication interface configured to facilitate communication between the second network node 105 and other nodes or devices, for example, UE 101 and / or the first network node 103 and / or the third network node 108, or other structures. The interface may include, for example, a transceiver configured to transmit and receive radio signals via an air interface in accordance with a suitable standard. In other embodiments, the second network node 105 may comprise the arrangement shown in Figure 8B. The second network node 105 may comprise a third processing circuit 711, for example, one or more processors such as the third processor 701, in the second network node 105 and the third memory 703. The second network node 105 may also comprise a third radio circuit 713, which may comprise, for example, the third receive port 704 and the third send port 705. The third processing circuit 711 may be configured to, or operable to, carry out the actions of the method according to Figure 5 in a manner similar to that described in relation to Figure 8A. The third radio circuit 713 PLnfr / n / Lznz / q / Yi can be configured to establish and maintain at least one wireless connection with the second network node 105. Circuit can be understood here as a hardware component. Therefore, the modalities of this document also refer to the second network node 105 operational for operation in the communications system 100. The second network node 105 may comprise the third processing circuit 713 and the third memory 703. The third memory 703 contains instructions executable by said third processing circuit 713. The second network node 105 is further operational for carrying out the actions described in this document in relation to the second network node 105, for example, in Figure 5. PLnfr / n / Lznz / q / Yi More expansions and variations Telecommunications network connected through an intermediate network to a main computer according to some modalities. With reference to Figure 9, according to one modality, a communication system includes a telecommunications network 3210 such as communication system 100, for example, a 3GPP-type cellular network, comprising the access network 3211, such as a radio access network, and the core network 3214. The access network 3211 comprises a plurality of network nodes 105. For example, base stations. 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c can be connected to the core network 3214 via a wired or wireless connection 3215. A plurality of user equipment, such as UE 101, can be included in the communications system 100. In Figure 9, a first UE 3291 located in coverage area 3213c is configured to wirelessly connect to, or be sought by, the corresponding base station 3212c. A second UE 3292 in coverage area 3213a can wirelessly connect to the corresponding base station 3212a.Although this example illustrates a plurality of UE 3291, 3292, the described modalities are equally applicable to a situation where a single UE is in the coverage area or where a single UE is connecting to the corresponding base station 3212. Any of the UEs 3291, 3292 can be considered examples of UE 101. The 3210 telecommunications network is itself connected to the 3230 main computer, which may be incorporated into the hardware and / or software of a standalone server, a cloud-deployed server, a distributed server, or as processing resources in a server farm. The 3230 main computer may be owned or controlled by a service provider, or it may PLnfr / n / Lznz / q / Yi may be operated by or on behalf of the service provider. Connections 3221 and 3222 between the telecommunications network 3210 and the main computer 3230 may extend directly from the core network 3214 to the main computer 3230 or may go through an optional intermediate network 3220. The intermediate network 3220 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more subnets (not shown). The communication system in Figure 9 as a whole enables connectivity between the connected UEs 3291 and 3292 and the main computer 3230. This connectivity can be described as an out-of-the-box (OTT) connection 3250. The main computer 3230 and the connected UEs 3291 and 3292 are configured to communicate data and / or signaling over the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate networks 3220, and any additional infrastructure (not shown) as intermediaries. The OTT connection 3250 can be transparent in that the participating communication devices through which the OTT connection 3250 passes are unaware of the uplink and downlink routing. For example, the base station 3212 PLnfr / n / Lznz / q / Yi may not be, or need not be, informed about the past routing of an incoming downlink communication with data originating from the host computer 3230 to be forwarded, for example, delivered, to a connected UE 3291. Similarly, base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from UE 3291 to the host computer 3230. With regard to Figures 10-14 described below, it can be understood that the base station can be considered an example of the first network node 103. Figure 10 illustrates an example of a main computer communicating through a first network node 103 with a UE 101 through a partially wireless connection according to some modalities. The UE 101 and the first network node 103, for example, a base station and a main computer discussed in the preceding paragraphs, will now be described with reference to Figure 10. In the communication system 3330, as in the communication system 100, the main computer 3310 comprises hardware 3315, which includes the communication interface 3316 configured to establish and maintain a wired or wireless connection with an interface of a communication device other than the communication system 3300. The main computer 3310 further comprises the circuitry of PLnfr / n / Lznz / q / Yi processing 3318, which may have storage and / or processing capabilities. In particular, the 3318 processing circuit may comprise one or more programmable processors, ASICs, field-programmable gate arrays (FPGAs), or combinations thereof (not shown) adapted to execute instructions. The main computer 3310 further comprises software 3311, which is stored on or accessible by the main computer 3310 and executable by the processing circuit 3318. Software 3311 includes main application 3312. Main application 3312 can be used to provide a service to a remote user, such as UE 3330, connecting via OTT connection 3350, which terminates at UE 3330 and the main computer 3310. In providing the service to the remote user, main application 3312 can provide user data transmitted using OTT connection 3350. The 3300 communication system further includes the first network node 103, exemplified in Figure 10 as a base station 3320 provided in a telecommunications system and comprising hardware 3325 that enables it to communicate with the main computer 3310 and the UE 3330. The hardware 3325 may include the communication interface 3326 for configuring and maintaining a wired or wireless connection with an interface of different communication devices in the 3300 communication system, as well as the radio interface. PLnfr / n / Lznz / q / Yi 3327 to establish and maintain at least the wireless connection 3370 with the UE 101, exemplified in Figure 10 as a UE 3330 located within a coverage area served by the base station 3320. The communication interface 3326 can be configured to facilitate the connection 3360 to the main computer 3310. The connection 3360 can be direct or can pass through a core network (not shown in Figure 10) of the telecommunications system and / or through one or more intermediate networks outside the telecommunications system. In the modality shown, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrangements, or combinations thereof (not shown) adapted to execute instructions.The 3320 base station also has the 3321 software stored internally or accessible via an external connection. The 3300 communication system also includes the previously mentioned UE 3330. Its hardware 3335 may include a radio interface 3337 configured to establish and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The UE 3330's hardware 3335 further includes the processing circuit 3338, which may comprise one or more programmable processors, specific integrated circuits of PLnfr / n / Lznz / q / Yi application, field programmable gate assemblies or combinations thereof (not shown) adapted to execute instructions. The UE 3330 further comprises software 3331, which is stored in, or accessible by, the UE 3330 and executable by processing circuit 3338. Software 3331 includes client application 3332. Client application 3332 can be operated to provide a service to a human or non-human user through the UE 3330, with support from the host computer 3310. On the host computer 3310, a running host application 3312 can communicate with the running client application 3332 through the OTT connection 3350, which terminates at the UE 3330 and the host computer 3310. In providing the service to the user, client application 3332 can receive request data from the host application 3312 and provide user data in response to the request data.The OTT connection 3350 can transfer both request data and user data. The client application 3332 can interact with the user to generate the user data they provide. It is observed that the main computer 3310, the base station 3320, and the UE 3330 illustrated in Figure 10 may be similar or identical to the main computer 3230, one of the base stations 3212a, 3212b, 3212c, and one of the UEs 3291, 3292 in Figure 9, respectively. That is, the The internal workings of these entities can be as shown in Figure 10, and independently, the topology of the surrounding network can be that of Figure 9. In Figure 10, the OTT connection 3350 is drawn abstractly to illustrate communication between the host computer 3310 and the UE 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages through these devices. The network infrastructure can determine the routing, which can be configured to hide from the service provider's UE 3330 or 3310 host computer, or both. While the OTT connection 3350 is active, the network infrastructure can also make decisions that dynamically change the routing, for example, based on load balancing or network reconfiguration. The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the principles of the modes described throughout this description. One or more of the various modes enhance the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the final segment. More precisely, the principles of these modes can improve spectrum efficiency and latency, and thus provide benefits such as PLnfr / n / Lznz / q / Yi reduced user wait time, improved responsiveness, and extended battery life. A measurement procedure may be provided to monitor data rate, latency, and other factors that improve one or more modes. Additionally, an optional network functionality may be available to reconfigure the OTT 3350 connection between the 3310 host computer and the 3330 UE in response to variations in measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT 3350 connection may be implemented in the 3311 software and 3315 hardware of the 3310 host computer, or in the 3331 software and 3335 hardware of the 3330 UE, or both.In some modes, sensors (not shown) can be deployed on or in association with communication devices through which the OTT connection 3350 passes. The sensors can participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified above, or by supplying values ​​of other physical quantities from which the software 3311, 3331 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 3350 can include message format, relay settings, preferred routing, etc. The reconfiguration does not have to affect the base station 3320 and may be unknown or imperceptible to the base station. PLnfr / n / Lznz / q / Yi 3320. Such procedures and functionalities may be known and practiced in the art. In certain modalities, the measurements may involve the patented UE signaling that facilitates measurements of the main computer 3310 for performance, propagation times, latency, and the like. The measurements may be implemented in software 3311 and 3331 that causes messages, in particular empty or dummy messages, to be transmitted using the OTT connection 3350 while monitoring propagation times, errors, etc. Figure 11 illustrates an example of methods implemented in a communication system 100 that includes a main computer, a base station 103, and a UE 101. Figure 11 is a flowchart illustrating a method implemented in a communication system 100. The communication system 100 includes a main computer, a base station 103, and a UE 101, which may be those described with reference to Figure 9 and Figure 10. For the sake of simplicity in the present invention, only references to Figure 11 will be included in this section. In step 3410, the main computer provides user data. In substep 3411 (which may be optional) of step 3410, the main computer provides the user data by running a main application. In step 3420, the main computer initiates a transmission carrying the user data. PLnfr / n / Lznz / q / Yi to UE 101. In step 3430 (which may be optional), base station 103 transmits to UE 101 the user data carried in the transmission initiated by the host computer, according to the instructional modes described throughout this document. In step 3440 (which may also be optional), UE 101 runs a client application associated with the main application run by the host computer. Figure 12 illustrates methods implemented in a communication system 100 comprising a main computer, a base station 103, and a UE 101 according to certain embodiments. Figure 12 is a flowchart illustrating a method implemented in a communication system 100. The communication system 100 comprises a main computer, a base station 103, and a UE 101, which may be those described with reference to Figure 9 and Figure 10. For the sake of simplicity, only references to Figure 12 will be included in this section. In step 3510 of the method, the main computer provides user data. In an optional substep (not shown), the main computer provides the user data by executing a main application. In step 3520, the main computer initiates a transmission that carries the user data to the UE 101.The transmission can pass through base station 103, according to the teachings of the modalities. PLnfr / n / Lznz / q / Yi described throughout this description. In step 3530 (which may be optional), the UE 101 receives the user data carried in the transmission. Figure 13 illustrates methods implemented in a communication system 100 comprising a main computer, a base station 103, and a UE 101. Figure 13 is a flowchart illustrating a method implemented in a communication system 100. The communication system 100 includes a main computer, a first network node 103, and a UE 101, which may be those described with reference to Figure 9 and Figure 10. For the sake of simplicity, only references to Figure 13 will be included in this section. In step 3610 (which may be optional), the UE 101 receives input data provided by the main computer. Alternatively, in step 3620, the UE 101 provides user data. In substep 3621 (which may be optional) of step 3620, the UE provides the user data by running a client application.In substep 3611 (which may be optional) of step 3610, UE 101 runs a client application that provides user data in response to input data received from the host computer. When providing user data, the running client application may also consider user input received from the user, regardless of the specific manner in which it is provided. PLnfr / n / Lznz / q / Yi provided the user data, and the UE 101 initiates, in substep 3630 (which may be optional), the transmission of the user data to the main computer. In step 3640 of the method, the main computer receives the user data transmitted from the UE 101, in accordance with the teachings of the modalities described throughout this description. Figure 14 illustrates methods implemented in a communication system 100 comprising a main computer, a base station 103, and a UE 101. Figure 14 is a flowchart illustrating a method implemented in a communication system 100. The communication system 100 comprises a main computer, a base station 103, and a UE 101, which may be those described with reference to Figure 9 and Figure 10. For the sake of simplicity, only references to Figure 14 will be included in this section. In step 3710 (which may be optional), in accordance with the principles of the modalities described throughout this description, the base station 103 receives user data from the UE 101. In step 3720 (which may be optional), the base station 103 initiates transmission of the received user data to the main computer.In step 3730 (which may be optional), the main computer receives the user data carried in the transmission initiated by the base station. PLnfr / n / Lznz / q / Yi 103. Some of the modalities can be summarized as follows: A 103 base station configured to communicate with a UE 101. The 103 base station comprises a radio interface and processing circuitry configured to perform one or more of the actions described in this document as performed by the first 103 network node. A communication system 100 that includes a main computer comprising: • processing circuits configured to provide user data; and • a communication interface configured to forward user data to a cellular network for transmission to a UE 101, • the cellular network comprises a first network node 103 having a radio interface and a processing circuit, the base station processing circuit is configured to carry out one or more of the actions described in this document as carried out by the first network node 103. The communication system 100 may also include the first network node 103. The communication system 100 may also include the UE 101. The UE 101 is configured to communicate with the first network node 103. The communication system 100, where: PLnfr / n / Lznz / q / Yi • the main computer's processing circuitry is configured to run a main application, thereby providing user data; and • the UE 101 comprises processing circuitry configured to run a client application associated with the main application. A method implemented on a first network node 103, comprising one or more of the actions described herein as carried out by the first network node 103. A method implemented in a communication system 100 comprising a main computer, a base station 103 and a UE 101, wherein the method comprises: • on the main computer, provide user data; and • on the main computer, initiate a transmission carrying the user data to UE 101 through a cellular network comprising the first network node 103, wherein the first network node 103 performs one or more of the actions described herein as performed by the first network node 103. The method may also include: • at the first network node 103, transmit the user data. User data can be provided on the main computer running a main application, and PLnfr / n / Lznz / q / Yi the method may also include: • In UE 101, run a client application associated with the main application. A UE 101 configured to communicate with a first network node 103, the UE 101 comprising a radio interface and a processing circuit configured to carry out one or more of the actions described in this document as carried out by the UE 101. A communication system 100 that includes a main computer comprising: • processing circuits configured to provide user data; and • a communication interface configured to forward user data to a cellular network for transmission to a UE 101, • the UE 101 comprises a radio interface and a processing circuit, the UE processing circuit is configured to carry out one or more of the actions described in this document as carried out by the UE 101. The communication system 100 may also include the UE 101. The communication system 100 also includes a first network node 103 configured to communicate with UE 101. PLnfr / n / Lznz / q / Yi The communication system 100, where: • The main computer's processing circuitry is configured to run a main application, thereby providing user data; and • the UE's processing circuitry is configured to run a client application associated with the main application. A method implemented in a UE 101 that comprises one or more of the actions described in this document as carried out by the UE 101. A method implemented in a communication system 100 comprising a main computer, a first network node 103 and a UE 101, wherein the method comprises: • on the main computer, provide user data; and • on the main computer, initiate a transmission that carries the user data to UE 101 through a cellular network comprising base station 103. UE 101 performs one or more of the actions described in this document as performed by UE 101. The method may also include: • In UE 101, receive user data from the first network node 103. A UE 101 configured to communicate with a first network node 103, the UE 101 comprising a radio interface and processing circuitry configured to carry out PLnfr / n / Lznz / q / Yi one or more of the actions described in this document as carried out by the UE 101. A communication system 100 that includes a main computer comprising: • a communication interface configured to receive user data originating from a transmission from a UE 101 to a first network node 103, • the UE 101 comprises a radio interface and a processing circuit, the UE processing circuit is configured to: carry out one or more of the actions described in this document as carried out by the UE 101. The communication system 100 may also include the UE 101. The communication system 100 may further include the first network node 103. The first network node 103 comprises a radio interface configured to communicate with UE 101 and a communication interface configured to forward to the main computer the user data carried by a transmission from UE 101 to base station 103. The communication system 100, where: • The main computer's processing circuitry is configured to run a main application; and • The UE's processing circuitry is configured to run an associated client application PLnfr / n / Lznz / q / Yi with the main application, thus providing user data. The communication system 100, where: • The main computer's processing circuitry is configured to run a main application, thereby providing the request data; and • The UE's processing circuitry is configured to run a client application associated with the main application, thereby providing the user data in response to the request data. A method implemented in a UE 101 that comprises one or more of the actions described in this document as carried out by the UE 101. The method may also include: • provide user data; and • forward user data to a host computer via transmission to the first network node 103. A method implemented in a communication system 100 comprising a main computer, a first network node 103 and a UE 101, wherein the method comprises: • On the main computer, receive user data transmitted to the first network node 103 from UE 101. UE 101 performs one or more of the actions described in this document as performed by UE 101. The method may also include: PLnfr / n / Lznz / q / Yi • in UE 101, provide user data to the first network node 103. The method may also include: • on the UE 101, run a client application, thereby providing the user data to be transmitted; and • on the main computer, run a main application associated with the client application. The method may also include: • on the UE 101, run a client application; and • on the UE 101, receive input data to the client application, the input data is provided on the host computer by running a host application associated with the client application, • the client application provides the user data to be transmitted in response to the input data. A first network node 103 configured to communicate with a UE 101, wherein the first network node 103 comprises a radio interface and a processing circuit configured to carry out one or more of the actions described herein as carried out by the network node 103. A 100% communication system that includes a PLnfr / n / Lznz / q / Yi main computer comprising a communication interface configured to receive user data from a transmission from a UE 101 to a base station 103. The first network node 103 comprises a radio interface and a processing circuit. The processing circuit of the base station is configured to carry out one or more of the actions described herein as carried out by the first network node 103. The communication system 100 may also include the first network node 103. The communication system 100 may also include the UE 101. The UE 101 is configured to communicate with the first network node 103. The communication system 100 where: • The main computer's processing circuitry is configured to run a main application; • The UE 101 is configured to run a client application associated with the main application, thereby providing user data to be received by the main computer. A method implemented at a first network node 103, comprising one or more of the actions described herein as carried out by any of the first node of PLnfr / n / Lznz / q / Yi red 103. A method implemented in a communication system that includes a main computer, a first network node 103, and a UE 101, wherein the method comprises: • On the main computer, receive, from the first network node 103, user data originating from a transmission that the base station has received from UE 101. UE 101 performs one or more of the actions described in this document as performed by UE 101. The method may also include: • at the first network node 103, receive user data from UE 101. The method may also include: • At the first network node 103, initiate a transmission of the received user data to the main computer. The methods described in this document refer to obtaining UE capability as before MME 105 establishes the session to SGW 108, or electing the DCN. To obtain the UE LTE-M RAT type in the first message, eNB 130 sends the UE INITIAL MESSAGE to MME 105, or at least before MME 105 establishes the session to SGW 108. It is also possible that the network may want to handle the standard UE using CE in the same way it handles LTE-M UEs, when related to roaming load and blocking. A solution for this is also provided. PLnfr / n / Lznz / q / Yi Generally, all terms used in this document should be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or implied by the context in which they are used. All references to an element, apparatus, component, means, step, etc., should be clearly interpreted as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed in this document need not be carried out in the exact order stated, unless a step is explicitly described as following or preceding another step and / or it is implied that one step should follow or precede another. Any feature of any of the modalities described herein may be applied to any other modality, where appropriate. Likewise, any advantage of any modality may be applied to any other modality and vice versa. Other objectives, features, and advantages of the attached modalities will become clear from the following description. In general, the use of first, second, third, fourth and / or fifth in this document can be understood as an arbitrary way of denoting different elements or entities, PLnfr / n / Lznz / q / Yi and it can be understood that it does not confer a cumulative or chronological character on the nouns it modifies, unless otherwise indicated, according to the context. This document includes several modalities. It should be noted that the examples in this document are not mutually exclusive. It can be tacitly assumed that the components of one modality are present in another modality, and it will be obvious to someone skilled in the technique how those components can be used in the other modalities, e.g. The modalities described in this document are not limited to those listed above. Various alternatives, modifications, and equivalents may be used. Therefore, the modalities listed above should not be considered as limiting the scope of the modalities. A feature of one modality may be combined with one or more features of any other modality. The term "at least one of A and B" should be understood to mean only A, only B, or both A and B, where A and B are any parameter, number, indication used in this document, etc. It should be emphasized that the term comprises / comprises when used in this specification is taken to specify the presence of features, whole numbers, PLnfr / n / Lznz / q / Yi steps or components are declared, but this does not exclude the presence or addition of one or more features, whole numbers, steps, components, or groups thereof. It should also be noted that the words "a" or "an element" preceding "a" do not exclude the presence of a plurality of such elements. The term configured for use in this document may also be referred to as arranged, adapted, capable of, or operational for. It should also be emphasized that the steps of the methods can, without departing from the modalities of this document, be carried out in a different order than the order in which they appear in this document. ABBREVIATIONS IoT Internet of Things CAT-M Category M BL Reduced bandwidth Low complexity CE Coverage Improvement DCN CN dedicated PLnfr / n / Lznz / q / Yi LTE-M UEs An LTE-M indication is sent from RAN node 103 to MME 105 in UE CAPACITY INFORMATION INDICATION. The procedure can be as illustrated in Figure 1. EU category information indication The purpose of the EU category information procedure is to enable eNB 103 to provide the EU MME with category-related information. EU category information may be referred to as EU capacity information, EU category indication, or EU capacity indication. Figure 1 shows the EU category information procedure. Operation successful. The eNB 103, which controls a logical SI connection associated with UE, initiates the procedure by sending a UE CAPACITY INFORMATION INDICATION message to MME 105 that includes the UE capacity information. The UE CAPACITY INFORMATION INDICATION message may also include paging-specific UE capacity information within the UE radius capacity IE for paging. The UE capacity information received by MME 105 will replace the corresponding UE capacity information previously stored in MME 105 for UE 101, as described in TS 23.401. PLnfr / n / Lznz / q / Yi If the UE CAPACITY INFORMATION INDICATION message contains the LTE-M indication IE, the MME 105, if supported, will use it in accordance with TS 23.401. If UE 101 indicates support for UE application layer measurement, eNB 103 will include, if supported, the UE application layer measurement capability IE in the UE CAPABILITY INFORMATION INDICATION message. MME 105, if supported, will store and use the information when initiating UE application layer measurement. In TS 36.300, handling capacity is specified as shown in Figure 2: PLnfr / n / Lznz / q / Yi When is LTE-M indication required in CN? During the initial connection procedure, UE 101 performs a random access, and the first message from eNB 103 to the CN is the UE INITIAL MESSAGE. At this stage, eNB 103 does not have the UE's capacity information. MME 105 requests eNB 103 to query the UE's capacity in the Initial Context Configuration Request. MME 105 stores the UE's capacity information until UE 101 disconnects. SA2 introduced a new type of RAT for LTE-M in order to apply a separate billing model for traffic from an LTE-M UE and introduce identification and transparency requirements in roaming. To meet these requirements, MME 105 needs to indicate whether a UE 101 is category M1 / M2 to S-GW / P-GW 108 as a new RAT type in Create Session Request. MME 105 also needs to block incoming roaming for category M1 / M2 UEs on the initial connection if required by the carrier. However, with the current 3GPP solution, which uses the M1 / M2 category to allocate the new LTE-M RAT type in the core network, MME 105 can only obtain an explicit LTE indication in the UE CAPACITY INFORMATION INDICATION. This would lead to the following problems: In the connection procedure, when MME 105 receives the initial UE message, it will send a session creation request to SGW 108 and indicate to SGW 108 that this is for an LTE-M1 / M2 UE for the charge. However, the UE capacity, if not available on MME 105, can be received from eNB 103 after the Initial Context Configuration Request / Response (ICSR), which would arrive late. For block roaming of an M1 / M2 category UE, this would mean that UE 101 will always be accepted for the connection procedure, and when MME 105 receives UE capacity after ICSR, UE 101 can be detached. This means that the M category roaming UE can PLnfr / n / Lznz / q / Yi access the network for communication during the initial connection even though it should be blocked. For DCN selection, M1 / M2 category UEs may be routed to an incorrect DCN. UUT configuration is now by IMSI level; however, if an MBB USIM is inserted into an M1 / M2 category UE, and MME 105 in the incorrect DCN receives the UE's capabilities, a redirection may be necessary to direct UE 101 to the correct DCN. This requires additional network signaling, and the redirection may not occur immediately. In the current specification, the CN receives the indication for LTE-M1 / M2 category UE in UE Capacity Information after the UE context and user plane have been configured. It's too late. Solutions Before a UE 101 sends an Msgl, for example, the RACH Preamble, it has to determine what type of RACH resource to use. This information is transmitted via SIB2. If the UE 101 is a BL UE or a UE 101 with enhanced coverage, the eNB 103 would be aware of it during the random access procedure. PLnfr / n / Lznz / q / Yi One solution is the network-side solution: When the eNB 103 is aware that the UE 101 is a BL UE or an UE in enhanced coverage during the random access procedure, the eNB indicates this to the MME 105. Depending on the operator's policy, if the normal UE using CE is to be treated the same as the M1 / M2 category UE for payload, routing to DCN, or roaming handling purposes, MME 105 could use this indication as if the UE 101 were LTE-Type M on the CN network side. If MME 105 needs to be different and ensure that UE 101 is of category M1 / M2, you can request the initial capacity towards eNB 103. The drawback of this solution is the additional signage or some ambiguity. One solution is from the EU side: Similar to the indication for the support of In CE Mode B, provided in the RRCConnectionSetupComplete message, a new indication is introduced to inform the eNB 103 whether UE 101 is an M1 / M2 category UE or a standard category UE in CE. See details below. The eNB 103 can then include the LTE-M indication in the initial UE message. This indication should be available for implementation soon. PLnfr / n / Lznz / q / Yi RRCConnectionSetupCom.pl ete The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment. Signaling radio carrier: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: EU to E UTRAN RRCConnectionSetupComplete Message - ASN1START RRCConnectíonSetupComplete ::= SEQUENCE { rrc-Transactionldentifier RRC-Transactionldentifier, criticalExtensions CHOICE { c1 CHOICE] rrcConnectionSetupComplete-r8 RRCConnectionSetupComplete-r8-IEs, spare3 NULL, spare2 NULL, sparel NULL}, critlcalExtenslonsFuture SEQUENCE {} RRCConnectionSetupComplete-r8-IEs selectedPLMN-ldentity registeredMME dedicatedlnfoNAS nonCriticalExtension} SEQUENCE] INTEGER (1..maxPLMN-r11), RegisteredMME OPTIONAL, DedicatedlnfoNAS, RRCConnectionSetupComplete-v8aO-IEs OPTIONAL RRCConnectionSetupComplete-v8aO-IEs ::= SEQUENCE] lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCConnectionSetupComplete-v1020-IEs OPTIONAL} RRCConnectionSetupComplete-v1020-IEs ::= SEQUENCE { gummei-Type-r10 rlf-lnfoAvailable-r10 logMeasAvailable-r10 m-SubframeConfigReq-r10 nonCriticalExtension ENUMERATED {native, mapped} OPTIONAL, ENUMERATED {true} OPTIONAL, ENUMERATED {true} OPTIONAL, ENUMERATED {required, notRequired} OPTIONAL, RRCConnectionSetupComplete-v1130-IEs OPTIONAL I / U / 4U I ó RRCConnectionSetupComplete-v1130-IEs ::= SEQUENCE { connEstFa¡llnfoAva¡lable-r11 ENUMERATED {true} OPTIONAL, nonCriticalExtension RRCConnectionSetupComplete-v1250-IEs OPTIONAL RRCConnectionSetupComplete-v1250-IEs mobilityState-r12 mobilityHistoryAvail-r12 logMeasAvailableMBSFN-r12 nonCriticalExtension SEQUENCE{ ENUMERATED {normal, médium, high, spare} OPTIONAL, ENUMERATED {true} ENUMERATED {true} RRCConnectionSetupComplete-v1320-IEs OPTIONAL, OPTIONAL, OPTIONAL RRCConnectionSetupComplete-v1320-IEs ::= SEQUENCE { ce-ModeB-r13 ENUMERATED {supported} s-TMSI-r13 S-TMSI OPTIONAL, attachW¡thoutPDN-Connectivity-r13 ENUMERATED {true} OPTIONAL, up-CloT-EPS-Optimisation-rl3 cp-CloT-EPS-Optim¡sat¡on-r13 nonCriticalExtension ENUMERATED {true} ENUMERATED {true} RRCConnectionSetupComplete-v1330-IEs OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL RRCConnectionSetupComplete-v1330-IEs ::= SEQUENCE { ue-CE-NeedULGaps-rl 3 ENUMERATED {true} nonCriticalExtension RRCConnectionSetupComplete-v1430-IEs OPTIONAL, OPTIONAL RRCConnectionSetupComplete-v1430-IEs ::= SEQUENCE { dcn-ID-r14 INTEGER (0..65535) nonCriticalExtension RRCConnectionSetupComplete-v1530-IEs OPTIONAL, OPTIONAL RRCConnectionSetupComplete-v1530-IEs logMeasAvailableBT-r15 logMeasAvailableWLAN-r15 idleMeasAvailable-r15 flightPathlnfoAvailable-r15 connectTo5GC-r15 registeredAMF-r15 s-NSSAI-list-r15 ng-5G-S-TMSI-Bits-r15 ng-5G-S-TMSI-r15 ng-5G-S-TMSI-Part2-r15 ::= SEQUENCE { ENUMERATED {true} ENUMERATED {true} ENUMERATED {true} ENUMERATED {true} ENUMERATED {true} RegisteredAMF-r15 OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, SEQUENCE(SIZE (1 ,.maxNrofS-NSSAI-r15)) OF S-NSSAI-r15 OPTIONAL, CHOICE { NG-5G-S-TMSI-r15, BIT STRING (SIZE (8)) OPTIONAL, nonCriticalExtension RRCConnectionSetupComplete-v1540-IEs OPTIONAL RRCConnectionSetupComplete-v1540-IEs gummei-Type-v1540 guami-Type-r15 nonCriticalExtension ::= SEQUENCE { ENUMERATED {mappedFrom5G} ENUMERATED {native, mapped} SEQUENCE {} OPTIONAL, OPTIONAL, OPTIONAL 94 RegisteredMME ::= plmn-ldentity mmegi SEQUENCE{ PLMN-ldentlty OPTIONAL, BIT STRING (SIZE (16)), mmec} MMEC r ι nb / n / i ζηζ / ζι / γ RegisteredAMF-r15 ::= plmn-ldent¡ty-r15 amf-ldentifier-rl 5 SEQUENCE{ PLMN-ldentlty OPTIONAL, AMF-ldentifier-r15 -ASN1ST0P Descriptions of the RRCConnectionSetupComplete field i aitach WithoutPDÑ-Connectivity i This field is used to indicate that the UE performs a connection procedure without i PDN connectivity, as indicated by the upper layers and specified in TS 24.301. i cp-CloT-EPS-Optimisation i This field is included when the UE supports CloT EPS optimization of the control plane, as indicated by the upper layers, verTS 24.301. i ce-ModeB i Indicates whether the UE supports operation in CE mode B, as specified in TS I 36.306. i connectTo5GC i This field is not used in the specification. It will not be sent by the UE. i dcnÍD I The identity of the dedicated core network, see TS 23.401. i guami-Type i This field is used to indicate whether the included GUAMI is native (derived from native 5G-GUTI) or mapped (from EPS, derived from EPS GUTI). This field is used to indicate whether the included GUMMEI is native (assigned by EPC) or mapped. The value native indicates that the GUMMEI is native, mapped indicates that the GUMMEI is mapped from 2G / 3G identifiers, and mappedFrom5G indicates that the GUMMEI is mapped from 5G identifiers. A UE that sets gummei-Type-v1540 to mappedFrom5G will also include gummei-Type-r10 and set it as native. i idleMeasAvailable i Indication that the UE has idle mode measurement report available. i mmegi i Provides the group identity of the MME registered within the PLMN, as provided by the upper layers, see TS 23.003. The `i mobilityState` field indicates the mobility state of the UE (as defined in TS 36.304, clause 5.2.4.3) just before the UE transitions to the RRC_CONNECTED state. The UE displays a medium and high value when it is in the medium and high mobility states, respectively. Otherwise, the UE displays a normal value. ng-5G-S-TMSI-Part2................................................................................................................................................................................ i The leftmost 8 bits of 5G-S-TMSI. ri nb / n / i znz / zi / Yl· Descriptions of the RRCConnectionSetupComplete attacWWithoutPDN-Connectiviiy field This field is used to indicate that the UE performs a connection procedure without PDN connectivity, as indicated by the upper layers and specified in TS 24.301. cp-Clo T-EPS-Optimization This field is included when the UE supports CloT EPS control plane optimization, as indicated by the upper layers, verTS 24.301. ce-ModeB Indicates whether the UE supports operation in CE mode B, as specified in TS 36.306. connectTo5GC This field is not used in the specification. It will not be sent by the EU. dcnÍD For the identity of the dedicated core network, see TS 23.401. guami-Type This field is used to indicate whether the included GUAMI is native (derived from native 5G-GUTI) or mapped (from EPS, derived from EPS GUTI). gummei-Type This field is used to indicate whether the included GUMMEI is native (assigned by EPC) or mapped. The value "native" indicates that the GUMMEI is native, "mapped" indicates that the GUMMEI is mapped from 2G / 3G identifiers, and "mappedFrom5G" indicates that the GUMMEI is mapped from 5G identifiers. A UE that sets gummei-Type-v1540 to "mappedFrom5G" will also include gummei-Type-r10 and set it to native. registeredMME This field is used to transfer the GUMMEI from the MME where the UE is registered, as provided by the upper layers. rn-SubframeConfigReq If present, this field indicates whether the connection is being established for an RN and whether or not a subframe configuration is requested. seiectedPLMÑidentity PLMN index selected by the UE from the plmn-lidentityList fields included in SIB1.1 if the 1st PLMN is selected from the 1st plmn-lidentityList included in SIB1,2 if the 2nd PLMN is selected from the same plmn-lidentityList, or when there are no more PLMNs present within the same plmn-lidentityList, then the PLMN appears in the subsequent plmn-lidentityList within the same SIB1 and so on. Γ I Ob / O / I 7O7 / 3 / YL Descriptions of the RRCConnectionSetupComplete field i attacWWithoutPDN-Connection i This field is used to indicate that the UE performs a connection procedure without PDN connectivity, as indicated by the upper layers and specified in TS 24.301. ii cp-CloT-EPS-Optimisation i This field is included when the UE supports CloT EPS optimization of the control plane, as indicated by the upper layers, see TS 24.301. i ce-ModeB i Indicates whether the UE supports operation in CE mode B, as specified in TS I 36.306. i connectTo5GC i This field is not used in the specification. It will not be sent by the UE. i dcn-lD i The identity of the dedicated core network, see TS 23.401. i guami-Type i This field is used to indicate whether the included GUAMI is native (derived from native 5G-GUTI) or mapped (from EPS, derived from EPS GUTI). This field is used to indicate whether the included GUMMEI is native (assigned by EPC) or mapped. The value native indicates that the GUMMEI is native, mapped indicates that the GUMMEI is mapped from 2G / 3G identifiers, and mappedFrom5G indicates that the GUMMEI is mapped from 5G identifiers. A UE that sets gummei-Type-v1540 to mappedFromSG will also include gummei-Type-r10 and set it as native. sA / SSAZ-L / sf (i) This field is a list of S-NSSAIs as indicated by the upper layers. The UE i can report up to eight S-NSSAIs per NSSAI, see TS 23.003. i ue-CE-NeedULGaps i Indicates whether the UE needs uplink gaps during continuous uplink transmission in FDD as specified in TS 36.211 and TS 36.306. i up-CioT EPS Optimization i This field is included when the UE supports user plane CioT EPS optimization, as indicated by the upper layers, see TS 24.301. In the current specification, the CN receives the indication for LTE-M1 / M2 category UE in UE Capacity Information after the context has been configured PLnfr / n / Lznz / q / Yii from UE and the user plane. This is too late.

Claims

1. A method carried out by a first network node (103), wherein the method comprises: determining (404) to which user equipment category, UE, a UE (101) belongs, wherein the UE category is M or low complexity without reduced bandwidth, BL in coverage enhancement, CE; and providing (405, 502, 508) UE category information about the determined UE category to a second network node (105).

2. The method according to claim 1, wherein the determination (404) of the EU category comprises detecting the EU category in a random access procedure.

3. The method in accordance with any of the preceding claims, wherein the EU category is determined on the basis of an indication received from the EU (101).

4. The method in accordance with any of the preceding claims, wherein the first network node (103) determines that the UE (101) belongs to category M when it has not detected any non-BL indication in CE.

5. The method according to any of the preceding claims, comprising: receiving (403, 504), from the second network node PLnfr / n / Lznz / q / Yi 100 (105), an indication that the second network node (105) wishes to know the UE category information.

6. The method in accordance with any of the preceding claims, wherein when the first network node (103) detects that a special preamble is used, it determines that it is necessary to provide UE category information.

7. A first network node (103), adapted to: determine to which user equipment category, UE, a UE (101) belongs, wherein the UE category is M or without reduced bandwidth Low complexity, BL in coverage enhancement, CE; and to provide UE category information about the determined UE category to a second network node (105).

8. The first network node (103) according to claim 7, adapted to determine the UE category by detecting the UE category in a random access procedure.

9. The first network node (103) according to any of claims 7-8, adapted to determine the UE category based on an indication received from the UE (101).

10. The first network node (103) according to any of claims 7-9, wherein the first network node (103) determines that the UE (101) belongs to category M when it has not detected any non-BL indication in CE. PLnfr / n / Lznz / q / Yi 101 11. The first network node (103) according to any of claims 7-10, adapted to: receive, from the second network node (105), an indication that the second network node (105) wishes to know the EU category information.

12. The first network node (103) according to any of claims 7-11, adapted so that when the first network node (103) detects that a special preamble is used, then it is adapted to determine that UE capacity information has to be provided.

13. A method carried out by a second network node (105), wherein the method comprises: obtaining (405, 502), from the first network node (105), user equipment category (UE) information about which UE category a UE (101) belongs to, wherein the UE category is M or without reduced bandwidth, Low complexity, BL, or Coverage enhancement, CE; and providing (406) the UE category information to a third network node (108).

14. The method according to claim 13, comprising: determining (402) that the second network node (105) wishes to know the UE category information; and transmitting (403, 504), to the first network node (103), an indication that the second network node (105) wishes to know the UE category information.

15. The method according to any of claims 13-14, comprising: determining (407) whether to treat the UEs (101) of all categories in the same way or in a different way relating to at least one of charge and roaming.

16. The method according to claim 15, where the second network node (105) has determined that it should treat UEs (101) of a certain category differently from UEs (101) of other categories, then the second network node (105) requests UE capacity information from the first network node (103) of the UE (101).

17. The method according to any of claims 13-16, comprising: using (409) the EU category information to apply dedicated core network load, DCN, or a roaming policy.

18. A second network node (105) adapted to: obtain, from the first network node (105), user equipment category (UE) information, indicating to which UE category a UE (101) belongs, where the UE category is M or Low Complexity (BL) with no reduced bandwidth; and to provide the UE category information to a third network node (108). PLnfr / n / Lznz / q / Yii 103 19. The second network node (105) according to claim 18, adapted to: determine that the second network node (105) wishes to know the UE category information; and to transmit, to the first network node (103), an indication that the second network node (105) wishes to know the UE category information.

20. The second network node (105) according to any of claims 18-19, adapted to: determine whether to treat UEs (101) of all categories in the same way or in a different way related to at least one of the rates and roaming.

21. The second network node (105) according to claim 20, where the second network node (105) has determined that it should treat UEs (101) of a certain category differently from UEs (101) of other categories, then the second network node (105) is adapted to request from the first network node (103) UE capacity information from the UE (101).

22. The second network node (105) according to any of claims 18 to 21, adapted to: use the UE category information to apply load or roaming policy to the dedicated core network, DCN.

23. A computer program comprising instructions that, when executed on at least one processor, cause the at least one processor to carry out the method in accordance with any one of the modes 1-6.

24. A carrier comprising the computer program according to claim 23, wherein the carrier is an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

25. A computer program comprising instructions that, when executed on at least one processor, cause the at least one processor to carry out the method in accordance with any of the modalities 13-17.

26. A carrier comprising the computer program according to claim 25, wherein the carrier is an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

27. A method carried out by a user team, UE (101), wherein the method comprises: providing (401) an indication of the UE category to a first network node, wherein the UE category is M or low complexity without reduced bandwidth, BL in coverage enhancement, CE. PLnfr / n / Lznz / q / Yi 28. The method according to claim 105 27, wherein the indication is provided in a random access procedure or in a radio resource control (RRC) message.

29. A user equipment, UE, (101) adapted to: provide an indication of UE category information to a first network node, wherein the UE category is M or low complexity without reduced bandwidth, BL in coverage enhancement, CE.

30. EU in accordance with claim 29, wherein the indication is provided in a random access procedure or in a radio resource control (RRC) message.

31. A computer program comprising instructions that, when executed on at least one processor, cause the at least one processor to carry out the method in accordance with any of claims 27-28.

32. A carrier comprising the computer program according to claim 31, wherein the carrier is an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

Images