Handling error indications

Abstract

The name of the invention is'handling error indication '. A method performed by a core network node and a base station for sharing error information is disclosed. A method performed by a core network node includes initiating transmission of an error indication message to a base station connected to the core network node, where the error indication message includes identification information of a wireless device that is a source of an incoming message for which an error has been detected. A method performed by a base station includes initiating transmission of an error indication message to a core network node connected to the base station, where the error indication message includes identification information for a wireless device that is a source of an incoming message for which an error has been detected. A core network node and a base station configured to perform the method are also disclosed.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to methods and devices in a network, and in particular to a core network node, a base station, and a method for sharing error information in the core network node and the base station. Background Art

[0002] Generally, all terms used herein, unless clearly given and / or different meanings are implied from the context in which it is used, will be interpreted according to their common meanings in the relevant technical field. Unless otherwise clearly stated, all references to one / an / the element, equipment, assembly, parts, steps, etc. will be openly interpreted as referring to at least one instance of the element, equipment, assembly, parts, steps, etc. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless the steps are clearly described as after or before another step and / or the implicit steps must be after or before another step. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. From the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0003] The Error Indication procedure is initiated by a node to report detected errors in an incoming message (e.g., a message from a User Equipment (UE)) if these errors cannot be reported via a suitable failure message. Detected error types may include unknown, unexpected, and erroneous protocol data errors, such as transfer syntax errors, abstract syntax errors, and logic errors.

[0004] 3GPP TS 38.413 v15.2.0 NG-RAN Application Protocol (NGAP), incorporated herein by reference and available at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx?specificationId=3223 as of February 10, 2020, a document produced by the 3rd Generation Partnership Project provides relevant background on how the error indication process works.

[0005] There is currently a certain challenge. In the current technical specifications, as described in detail in 3GPP TS 38.413 v15.2.0, the error indication process only supports instances where the UE (user equipment, also referred to herein as a wireless device) is identified by one or more UE APIDs (i.e., application protocol IDs). Typically, a UE is identified by a UE APID pair, so when there is a UE with an associated connection (e.g., connected to an eNB, which itself is connected to an MME), there is an evolved Node B eNB, UE APID, and a mobility management entity MME, UE APID.

[0006] When UE APID is available, this form of UE ID is usually used to identify the UE. UE APID can be used even when other forms of UE APID are available. However, in some cases, especially but not excluding the case where UE APID is not available, a node (such as eNB, example of a base station) may use another form of identifier of the UE in a message sent to another node (such as a core network node). The error indication process in the current technical specification does not support other types of UE IDs. Other types of UE IDs that can be used by the eNB include S-TMSI (i.e., System Architecture Evolution Temporary Mobile Subscriber Identifier) ​​in LTE (Long Term Evolution) systems, and the 5th generation S-TMSI (5G-S-TMSI).

[0007] The eNB may communicate with the core network using only a UE ID (or multiple UE IDs) that is not the UE APID, for example, in a "retrieve UE information" message sent over the S1 interface (e.g. Figure 1 As shown, where only the S-TMSI is used to identify the UE). If the core network node (e.g., the mobility management entity MME) is unaware of the S-TMSI, then it is unknown where the core network node should send the error indication message to the eNB, and the core network node (e.g., the MME) may not be able to indicate to the eNB which UE is the source of the incoming message that has detected an error; the core network node may also not be able to accurately indicate what error was detected. The opposite is also true, whereby the core network node sends a UE information transfer message containing the S-TMSI to the eNB, and if the eNB is unaware of the S-TMSI, the eNB may not be able to correctly send an error indication message in response. Summary of the invention

[0008] It is an object of the present disclosure to improve the sharing of error information, thereby improving the efficiency with which errors can be identified, reported, and resolved.

[0009] According to some embodiments, a method for sharing error information performed by a core network node is provided, the method comprising: initiating transmission of an error indication message to a base station connected to the core network node, wherein the error indication message includes identification information of a wireless device that is the source of an incoming message for which an error has been detected.

[0010] According to some embodiments, a method for sharing error information performed by a mobility management entity MME is provided, the method comprising: initiating transmission of an error indication message to an evolved Node B eNB connected to the MME: wherein the error indication message comprises identification information of a wireless device which is the source of an incoming message in which an error has been detected; wherein the identification information comprises a System Architecture Evolution Temporary Mobile Subscriber Identifier S-TMSI of the wireless device; and wherein the eNB and the MME use an S1 application protocol S1AP or a next generation application protocol NGAP.

[0011] According to some embodiments, a method for sharing error information performed by a base station is provided, the method comprising: initiating transmission of an error indication message to a core network node connected to the base station, wherein the error indication message includes identification information of a wireless device that is the source of an incoming message for which an error has been detected.

[0012] According to some embodiments, a method for sharing error information performed by an evolved Node B (eNB) is provided, the method comprising: initiating transmission of an error indication message to a mobility management entity (MME) connected to the eNB; wherein the error indication message comprises identification information of a wireless device which is the source of an incoming message in which an error has been detected; wherein the identification information comprises a System Architecture Evolution Temporary Mobile Subscriber Identifier (S-TMSI) of the wireless device; and wherein the eNB and the MME use an S1 application protocol (S1AP) or a next generation application protocol (NGAP).

[0013] Further embodiments provide a core network node, an MME, a base station and an eNB configured to perform the method. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] For a better understanding of the present disclosure, and to show how the same may be implemented, reference will now be made, by way of example only, to the accompanying drawings, in which: Figure 1 shows a request for UE information sent by the eNB via the S1 interface; Figure 2 is a schematic diagram of a wireless network according to some embodiments; Figure 3 is a schematic diagram of a user equipment according to some embodiments; Figure 4is a schematic diagram of a virtualization environment according to some embodiments; Figure 5 is a schematic diagram of a telecommunications network connected to a host computer via an intermediate network according to some embodiments; Figure 6 is a schematic diagram of a host computer communicating with a user device via a base station through a partially wireless connection according to some embodiments; Figure 7 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; Figure 8 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; Fig. 9 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; Fig.10 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; Fig.11 is a flow chart of a method according to some embodiments; Fig.12 is a schematic diagram of a virtualized device according to some embodiments; Fig.13 is a flowchart of another method according to some embodiments; and Fig.14 is a schematic diagram of another virtualization device according to some embodiments. DETAILED DESCRIPTION

[0015] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges.

[0016] A UE ID (e.g., S-TMSI or 5G-S-TMSI) in addition to the UE APID may be included in the error indication. In the case where a UE APID is not assigned and only another UE ID (e.g., S-TMSI) is used in messages such as a "Retrieve UE Information" message or a "UE Information Transfer" message, a node (e.g., a core network node) that receives the message and detects an error may issue an error indication message that locates which UE is the source of the incoming message in which the error has been detected. The node that sent the message (i.e., the Retrieve UE Information message) may receive an error indication that includes a UE ID instead of a UE APID, and may use the content of the error indication message to construct the following message accordingly. As an example of this situation, when an unknown UE APID is optionally present in a subsequent message, the node may not include the unknown UE APID.

[0017] In summary, when the UE is not identified by the UE AP ID(s), a node detecting an error may be able to send a useful error indication.

[0018] Various embodiments are presented herein that address one or more of the issues disclosed herein. An embodiment provides a method for sharing error information performed by a core network node, the method comprising: initiating transmission of an error indication message to a base station connected to the core network node, wherein the error indication message includes identification information of a wireless device that is the source of an incoming message for which an error has been detected. The error indication message may include a UE identity element, which may specify whether one or more UE identity formats are used with a digital reference to a UE identity format, or where UE identity formats are listed. By providing an indication to a base station (potentially in response to a message sent by the base station, such as a retrieve UE information message) of a wireless device identifier that is unknown to the core network node, the efficiency of future communications may be improved. As an example, the base station may omit unknown UE identity information from subsequent messages, thereby reducing the probability that additional error indication messages are needed.

[0019] An embodiment provides a method for sharing error information performed by a base station, the method comprising: initiating transmission of an error indication message to a core network node connected to the base station, wherein the error indication message includes identification information of a wireless device that is the source of an incoming message for which an error has been detected. The error indication message may include a UE identity element, which may specify whether one or more UE identity formats are used with a digital reference for a UE identity format, or where the UE identity formats are listed. By providing an indication to the core network node (possibly in response to a message sent by the core network node, such as a UE information transfer message) of a wireless device identifier that is unknown to the base station, the efficiency of future communications may be improved. As an example, the core network node may omit the unknown UE identity information from subsequent messages and thereby reduce the probability that additional error indication messages are needed.

[0020] Certain embodiments may provide one or more of the following technical advantages. When APID is not used and other UE IDs (such as S-TMSI or 5G-S-TSMI) are used, the node detecting the error can indicate the correct UE. This information may be important for the node sending the retrieve UE information message or the UE information transfer message, so that the node sending the retrieve UE information message or the UE information transfer message is informed of what error occurred when the node (which may be MME, eNB, etc.) received the retrieve UE information or UE information transfer message.

[0021] Additional Notes Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document(s) provided in the appendix.

[0022] In various aspects of the embodiments, any suitable UE ID may be included in the error indication process so that when a node (e.g., a base station) detects an error, it may use a given one or more UE IDs to send an error indication message to a (further) base station or core network node. Thus, the error indication message may include, for example, S-TMSI and / or IMSI as one or more UE IDs. In a 5G system, 5G-S-TMSI may be used. The error indication message may be sent by a node (e.g., a core network node) that has detected an error in response to a message from a base station (e.g., retrieving a UE information message). Typically, the error indication message may be sent between nodes.

[0023] In addition to the APID, UE IDs that may be included in a message addressing a specific UE include S-TMSI and 5G-S-TMSIUE IDs. Other suitable UE IDs may be included additionally or alternatively. An example implementation in an aspect of an embodiment in an LTE system is where the UE's S-TMSI is added to an error indication of the S1AP, for example as an additional element in a message. The error indication message format as in Section 9.1.8.3 of 3GPP TS 36.413 V14.8.0 (available at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx?specificationId=2446 on February 10, 2020) is shown in the summary below; in Table 1, the message format includes an additional element of the S-TMSI UE ID as described above (shown in the bottom row of Table 1). The S-TMSI is optional and is indicated by an "O" in the presence column.

[0024] 9.1.8.3 Error Indication This message is sent by both the MME and the eNB and is used to indicate that a certain error has been detected in the node.

[0025] Direction: MME→eNB and eNB→MME Table 1: S-TMSI included in the error indication in Chapter 9.1.8.3 of S1AP In various aspects of the embodiments, a more general UE identity may be introduced. In these aspects of the embodiments, the presence of various UEID formats such as S-TMSI, 5G-S-TMSI, etc. may be indicated using an enumerated value or as a selection list. The message format of Section 9.1.8.3 of 3GPP TS 36.413 V14.8.0 modified to include a message format is shown in Table 2 below, where the message format includes an additional element that includes an enumerated list as described above (shown in the bottom row of Table 2). Another aspect of the embodiment is shown in Table 3, which shows additional elements that can be added to the error indication message to provide a list format.

[0026] 9.1.8.3 Error Indication This message is sent by both the MME and the eNB and is used to indicate that a certain error has been detected in the node.

[0027] Direction: MME→eNB and eNB→MME Table 2: Inclusion of UE identity xyz in the error indication in chapter 9.1.8.3 in S1AP UE Identity IE / Group Name exist scope IE Types and References Semantic Description CHOICE UE identity M 9.2.1.1 >S-TMS / >>S-TMSI M 9.2.3.6 >IMSI >>IMSI M 9.2.3.11 Table 3: Use the format list to indicate the UE ID format.

[0028] Although the above aspects of the embodiments discuss modifications to the error indication message of S1AP, it will be understood that the modifications discussed are equally applicable to systems using NGAP. In addition, although the above aspects of the embodiments primarily relate to T-TMSI and 5G-T-TMSI, it will be understood that other UEID formats in addition to (one or more) UE APIDs may be added to the error indication in addition or alternatively. The selection of which UE ID formats to add to the error indication message may depend on the specific requirements of the system utilizing the error indication message.

[0029] The node sending a message (e.g., a UE Information Delivery message or a Retrieve UE Information message) may use feedback in the error indication from the node receiving the message. Take, for example, a base station (e.g., an eNB) sending a "Retrieve UE Information" message to a core network node (e.g., an MME); when the eNB receives a returned error indication from the MME, the eNB then knows which S-TMSI is unknown to the MME. The eNB may then use this feedback information to configure subsequent messages sent to the MME. As an example of configuration of subsequent messages, the eNB may not include the S-TMSI in subsequent messages such as an initial UE message, where the presence of the S-TMSI is optional.

[0030] If an unknown S-TMSI is included in the Initial UE message, the MME may perform a search for the S-TMSI and (upon failure to find the unknown S-TMSI) may reject the Initial UE message. The MME may reject an Initial UE message including an unknown S-TMSI, since the criticality of its assignment is "reject" if an unknown S-TMSI is included; according to the specification, the MME shall then issue a new error indication and the S1 connection shall not be established.

[0031] By omitting the (optional) unknown S-TMSI, the eNB can avoid rejecting the initial UE message. If the eNB does not include the S-TMSI in this case, the MME will successfully establish the S1 connection (assuming no other problems exist) and can continue to establish the UE context and user plane.

[0032] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Figure 2 For simplicity, Figure 2 The wireless network of FIG. 1 depicts only network 206 (including at least one core network node as described above, which may be an MME), network nodes 260 and 260b, and WDs 210, 210b, and 210c. In practice, the wireless network may further include any additional elements suitable for supporting communications between wireless devices or between a wireless device and another communication device, such as a landline phone, a service provider, or any other network node or end device. In the components shown, network node 260 and wireless device (WD) 210 are depicted with additional details. The wireless network may provide communications and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by or via the wireless network.

[0033] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G or 5G standards; Wireless Local Area Network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and / or ZigBee standards.

[0034] Network 206 may include one or more backhaul networks, core networks (including core network nodes), IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0035] The network node 260 and WD 210 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in transmitting data and / or signals via a wired or wireless connection.

[0036] As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to implement and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the amount of coverage they provide (or, in other words, their transmit power levels), and then may also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as a radio device with an integrated antenna. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Still other examples of network nodes include multi-standard radio (MSR) equipment (such as an MSR BS), a network controller (such as a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to implement and / or provide a wireless device with access to a wireless network or to provide a certain service to a wireless device that has accessed a wireless network.

[0037] exist Figure 2 In the embodiment, the network node 260 includes a processing circuit 270, a device readable medium 280, an interface 290, an auxiliary device 284, a power supply 286, a power circuit 287 and an antenna 262. Figure 2The network node 260 shown in the example wireless network of can represent a device including the illustrated combination of hardware components, but other embodiments can include network nodes with different combinations of components. It is to be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 260 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node can include multiple different physical components that make up the single illustrated component (for example, the device readable medium 280 can include multiple separate hard drives and multiple RAM modules).

[0038] Similarly, the network node 260 may be composed of multiple physically separated components (e.g., NodeB components and RNC components or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some cases where the network node 260 includes multiple individual components (e.g., BTS and BSC components), one or more of the individual components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In this case, each unique NodeB and RNC pair may be considered a single individual network node in some instances. In some embodiments, the network node 1360 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be repeated (e.g., separate device readable storage media 280 for different RATs), and some components may be reused (e.g., RATs may share the same antenna 262). The network node 260 may also include multiple sets of various illustrated components for different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into the network node 260. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 260 .

[0039] The processing circuit 270 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuit 270 may include processing information obtained by the processing circuit 270, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and making a determination as a result of the processing.

[0040] The processing circuitry 270 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide network node 260 functionality, alone or in conjunction with other network node 260 components, such as device readable medium 280. For example, the processing circuitry 270 may execute instructions stored in the device readable medium 280 or in a memory within the processing circuitry 270. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 270 may include a system on a chip (SOC).

[0041] In some embodiments, processing circuitry 270 may include one or more of radio frequency (RF) transceiver circuitry 272 and baseband processing circuitry 274. In some embodiments, radio frequency (RF) transceiver circuitry 272 and baseband processing circuitry 274 may be on separate chips (or chipsets), boards, or units (such as a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuitry 272 and baseband processing circuitry 274 may be on the same chip or chipset, board, or unit.

[0042] In certain embodiments, some or all of the functionality described herein as provided by a network node, base station, eNB, or other such network device may be performed by a processing circuit 270 executing instructions stored in a memory or device-readable medium 280 within the processing circuit 270. In alternative embodiments, some or all of the functionality may be provided by the processing circuit 270, such as in a hardwired manner, without the need to execute instructions stored on a separate or discrete device-readable medium. In any of those embodiments, the processing circuit 270 can be configured to perform the described functionality, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 270 alone or other components of the network node 260, but are enjoyed by the network node 260 as a whole, and / or generally by end users and wireless networks.

[0043] The device-readable medium 280 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuit 270. The device-readable medium 280 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by the processing circuit 270 and utilized by the network node 260. The device-readable medium 280 may be used to store any calculations performed by the processing circuit 270 and / or any data received via the interface 290. In some embodiments, the processing circuit 270 and the device-readable medium 280 may be considered integrated.

[0044] Interface 290 is used in wired or wireless communication of signaling and / or data between network node 260, network 206 and / or WD 210. As shown, interface 290 includes (one or more) ports / (one or more) terminals 294, to send data to network 206 and receive data from network 206 through wired connection, for example. Interface 290 also includes radio front-end circuit 292, which can be coupled to antenna 262, or is a part of antenna 262 in some embodiments. Radio front-end circuit 292 includes filter 298 and amplifier 296. Radio front-end circuit 292 can be connected to antenna 262 and processing circuit 270. Radio front-end circuit can be configured to adjust the signal transmitted between antenna 262 and processing circuit 270. Radio front-end circuit 292 can receive digital data to be sent to other network nodes or WD via wireless connection. Radio front-end circuit 292 can use a combination of filter 298 and / or amplifier 296 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. Then, the radio signal can be transmitted via antenna 262. Similarly, when data is received, antenna 262 may collect radio signals, which are then converted into digital data by radio front end circuitry 292. The digital data may be passed to processing circuitry 270. In other embodiments, the interface may include different components and / or different combinations of components.

[0045] In some alternative embodiments, the network node 260 may not include a separate radio front end circuit 292, and instead, the processing circuit 270 may include the radio front end circuit and may be connected to the antenna 262 without the separate radio front end circuit 292. Similarly, in some embodiments, all or some of the RF transceiver circuit 272 may be considered part of the interface 290. In still other embodiments, the interface 290 may include one or more ports or terminals 294, the radio front end circuit 292, and the RF transceiver circuit 272 as part of a radio unit (not shown), and the interface 290 may communicate with the baseband processing circuit 274, which is part of the digital unit (not shown).

[0046] Antenna 262 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 262 may be coupled to radio front-end circuit 290 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 262 may include one or more omnidirectional, sector or flat panel antennas operable to transmit / receive, for example, radio signals between 2 GHz and 66 GHz. Omnidirectional antennas may be used to transmit / receive radio signals in any direction, sector antennas may be used to transmit / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for transmitting / receiving radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 262 may be separate from network node 260 and may be connected to network node 260 via an interface or port.

[0047] Antenna 262, interface 290 and / or processing circuit 270 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 262, interface 290 and / or processing circuit 270 can be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data and / or signal can be transmitted to a wireless device, another network node and / or any other network equipment.

[0048] The power circuit 287 may include or be coupled to a power management circuit and is configured to supply power for performing the functionality described herein to the components of the network node 260. The power circuit 287 may receive power from the power supply 286. The power supply 286 and / or the power circuit 287 may be configured to provide power to the various components of the network node 260 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 286 may be included in the power circuit 287 and / or the network node 260 or outside the power circuit 287 and / or the network node 260. For example, the network node 260 may be connected to an external power source (e.g., an electrical socket) via an input circuit or interface (such as a cable), whereby the external power source supplies power to the power circuit 287. As another example, the power supply 286 may include a power source in the form of a battery or a battery pack, which is connected to the power circuit 287 or integrated in the power circuit 287. If the external power supply fails, the battery may provide a backup power source. Other types of power sources, such as photovoltaic devices, may also be used.

[0049] Alternative embodiments of network node 260 may include, in addition to Figure 2 , which may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 260 may include a user interface device to allow information to be input into the network node 260 and to allow information to be output from the network node 260. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on the network node 260.

[0050] Wireless device (WD) or user equipment (UE) used in this article refers to a device that can, is configured to, is arranged to and / or is operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise noted, the term WD is used interchangeably with user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to transmit and / or receive wireless signals. In some embodiments, the WD may be configured to transmit and / or receive information without direct human interaction. For example, the WD may be designed to transmit information to the network according to a predetermined schedule when triggered by an internal or external event, or in response to a request from the network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted wireless terminal devices, etc. For example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), WDs can support device-to-device (D2D) communication, and in this case WDs can be referred to as D2D communication devices. As another specific example, in the case of the Internet of Things (IoT), WDs can represent machines or other devices that perform monitoring and / or measurement, and transmit the results of such monitoring and / or measurement to another WD and / or network node. In this case, WDs can be machine-to-machine (M2M) devices, which can be referred to as MTC devices in the 3GPP context. As a specific example, a WD may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, a WD may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation. A WD as described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. In addition, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0051] As shown, wireless device 210 includes antenna 211, interface 214, processing circuit 220, device readable medium 230, user interface device 232, auxiliary device 234, power supply 236 and power circuit 237. WD 210 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 210, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technology, just to mention a few. These wireless technologies can be integrated into chips or chipsets that are the same or different from other components in WD 210.

[0052] Antenna 211 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 214. In some alternative embodiments, antenna 211 may be separated from WD 210 and may be connected to WD 210 via an interface or port. Antenna 211, interface 214, and / or processing circuit 220 may be configured to perform any receiving or transmitting operation described herein as being performed by WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 211 may be considered as an interface.

[0053] As shown, the interface 214 includes a radio front-end circuit 212 and an antenna 211. The radio front-end circuit 212 includes one or more filters 218 and an amplifier 216. The radio front-end circuit 214 is connected to the antenna 211 and the processing circuit 220, and is configured to adjust the signal transmitted between the antenna 211 and the processing circuit 220. The radio front-end circuit 212 may be coupled to the antenna 211 or may be part of the antenna 211. In some embodiments, the WD 210 may not include a separate radio front-end circuit 212; instead, the processing circuit 220 may include a radio front-end circuit and may be connected to the antenna 211. Similarly, in some embodiments, some or all of the RF transceiver circuit 222 may be considered to be part of the interface 214. The radio front-end circuit 212 may receive digital data to be sent out to other network nodes or WDs via a wireless connection. The radio front-end circuit 212 may use a combination of filters 218 and / or amplifiers 216 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via the antenna 211. Similarly, when data is received, antenna 211 may collect radio signals, which are then converted into digital data by radio front end circuit 212. The digital data may be passed to processing circuit 220. In other embodiments, the interface may include different components and / or different combinations of components.

[0054] Processing circuit 220 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide WD 210 functionality alone or in conjunction with other WD 210 components (such as device readable medium 230). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuit 220 may execute instructions stored in device readable medium 230 or in a memory within processing circuit 220 to provide functionality disclosed herein.

[0055] As shown, the processing circuit 220 includes one or more of the RF transceiver circuit 222, the baseband processing circuit 224, and the application processing circuit 226. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 220 of the WD 210 may include a SOC. In some embodiments, the RF transceiver circuit 222, the baseband processing circuit 224, and the application processing circuit 226 may be on a separate chip or chipset. In alternative embodiments, part or all of the baseband processing circuit 224 and the application processing circuit 226 may be combined into one chip or chipset, and the RF transceiver circuit 222 may be on a separate chip or chipset. In some alternative embodiments, part or all of the RF transceiver circuit 222 and the baseband processing circuit 224 may be on the same chip or chipset, and the application processing circuit 226 may be on a separate chip or chipset. In some alternative embodiments, part or all of the RF transceiver circuit 222, the baseband processing circuit 224, and the application processing circuit 226 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry 222 may be part of interface 214. RF transceiver circuitry 222 may condition RF signals for processing circuitry 220.

[0056] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by a processing circuit 220 executing instructions stored on a device-readable medium 230, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuit 220, such as in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of those specific embodiments, the processing circuit 220 can be configured to perform the described functionality, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 220 alone or other components of the WD 210, but are enjoyed by the WD 210 as a whole, and / or are generally enjoyed by end users and wireless networks.

[0057] Processing circuit 220 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations performed by processing circuit 220 may include processing information obtained by processing circuit 220, such as by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 210, and / or performing one or more operations based on the obtained information or the converted information and making a determination as a result of the processing.

[0058] The device-readable medium 230 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc., and / or other instructions executable by the processing circuit 220. The device-readable medium 230 may include a computer memory (e.g., a random access memory (RAM) or a read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disk (CD) or a digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 220. In some embodiments, the processing circuit 220 and the device-readable medium 230 may be considered integrated.

[0059] The user interface device 232 can provide a component that allows a human user to interact with the WD 210. This interaction can have a variety of forms, such as visual, auditory, tactile, etc. The user interface device 232 can be operable to generate output to the user and allow the user to provide input to the WD 210. The type of interaction can vary according to the type of user interface device 232 installed in the WD 210. For example, if the WD 210 is a smart phone, the interaction can be carried out via a touch screen; if the WD 210 is a smart meter, the interaction can be carried out through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 232 may include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface device 232 is configured to allow information to be input into the WD 210, and is connected to the processing circuit 220 to allow the processing circuit 220 to process the input information. The user interface device 232 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port or other input circuits. The user interface device 232 is also configured to allow information to be output from the WD 210, and allows the processing circuit 220 to output information from the WD 210. The user interface device 232 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 232, the WD 210 can communicate with an end user and / or a wireless network, and allow them to benefit from the functionality described herein.

[0060] Auxiliary device 234 is operable to provide more specific functionality that may not normally be performed by a WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communications such as wired communications, etc. The inclusion and type of components of auxiliary device 234 may vary depending on the embodiment and / or situation.

[0061] In some embodiments, the power supply 236 may take the form of a battery or battery pack. Other types of power supplies may also be used, such as an external power supply (e.g., an electrical socket), a photovoltaic device, or a power battery. The WD 210 may further include a power circuit 237 for delivering power from the power supply 236 to the various parts of the WD 210 that need power from the power supply 236 to perform any functionality described or indicated herein. In some embodiments, the power circuit 237 may include a power management circuit. The power circuit 237 may additionally or alternatively be operable to receive power from an external power supply; in this case, the WD 210 may be connected to an external power supply (such as an electrical socket) via an input circuit or interface (such as a power cable). In some embodiments, the power circuit 237 may also be operable to deliver power from an external power supply to the power supply 236. For example, this may be used for charging the power supply 236. The power circuit 237 may perform any formatting, conversion, or other modifications to the power from the power supply 236 so that the power is suitable for the corresponding components of the WD 210 that is supplied with power.

[0062] Figure 3 An embodiment of a UE according to various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Alternatively, a UE may represent a device that is intended to be sold to or operated by a human user, but the device may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart meter). UE 300 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 3 The UE 300 illustrated in FIG. 1 is an example of a WD configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 3 It is a UE, but the components discussed in this article are also applicable to WD, and vice versa.

[0063] exist Figure 3In the embodiment, UE 300 includes processing circuit 301, which is operably coupled to input / output interface 1605, radio frequency (RF) interface 309, network connection interface 311, memory 315 including random access memory (RAM) 317, read-only memory (ROM) 319 and storage medium 321, communication subsystem 331, power supply 333 and / or any other components or any combination thereof. Storage medium 321 includes operating system 323, application 325 and data 1627. In other embodiments, storage medium 321 may include other similar types of information. Some UEs may utilize Figure 3 All components shown in the UE may be used, or only a subset of the components may be used. The degree of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0064] exist Figure 3 , processing circuit 301 may be configured to process computer instructions and data. Processing circuit 301 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as microprocessors or digital signal processors (DSPs), together with appropriate software; or any combination of the above. For example, processing circuit 301 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0065] In the depicted embodiment, the input / output interface 305 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 300 may be configured to use an output device via the input / output interface 305. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to the UE 300 and output from the UE 300. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 300 may be configured to use an input device via the input / output interface 305 to allow a user to capture information into the UE 300. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a roller, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. For example, the sensor can be an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0066] exist Figure 3 In the embodiment of the present invention, the RF interface 309 can be configured to provide a communication interface to the RF components (such as transmitters, receivers and antennas). The network connection interface 311 can be configured to provide a communication interface to the network 343a. The network 343a can cover wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunication networks, another similar network or any combination thereof. For example, the network 343a can include a Wi-Fi network. The network connection interface 311 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 311 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

[0067] RAM 317 can be configured to interface with processing circuit 301 via bus 302 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications and device drivers. ROM 319 can be configured to provide computer instructions or data to processing circuit 301. For example, ROM 319 can be configured to store unchanged low-level system code or data of basic system functions stored in non-volatile memory, and basic system functions such as basic input and output (I / O), startup or receiving keystrokes from keyboard. Storage medium 321 can be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette or flash drive. In one example, storage medium 321 can be configured to include operating system 323, application 325 (such as web browser application, widget or gadget engine or another application) and data file 327. The storage medium 321 may store any of various operating systems or combinations of operating systems for use by the UE 300 .

[0068] The storage medium 321 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (such as a subscriber identity module or a removable user identity (SIM / RUIM) module), other memory or any combination thereof. The storage medium 321 may allow the UE 300 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article such as utilizing a communication system may be tangibly embodied in the storage medium 321, which may include a device-readable medium.

[0069] exist Figure 3In the embodiment, the processing circuit 301 can be configured to communicate with the network 343b using the communication subsystem 331. The network 343a and the network 343b can be the same one or more networks or different one or more networks. The communication subsystem 331 can be configured to include one or more transceivers for communicating with the network 343b. For example, the communication subsystem 331 can be configured to include one or more transceivers for communicating with the network 343b according to one or more communication protocols (such as IEEE 802.14, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.) and one or more remote transceivers of another device (such as another WD, UE or base station of a radio access network (RAN)) capable of wireless communication. Each transceiver may include a transmitter 333 and / or a receiver 335 to respectively implement the transmitter or receiver functionality (e.g., frequency allocation, etc.) suitable for the RAN link. In addition, the transmitter 333 and the receiver 335 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0070] In the illustrated embodiment, the communication functions of the communication subsystem 331 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine the location, another similar communication function or any combination thereof. For example, the communication subsystem 331 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 343b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network 343b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 313 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 300.

[0071] The features, benefits and / or functions described herein may be implemented in one of the components of the UE 300, or divided across multiple components of the UE 300. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 331 may be configured to include any component described herein. In addition, the processing circuit 301 may be configured to communicate with any such component via the bus 302. In another example, any of such components may be represented by program instructions stored in a memory, which perform corresponding functions described herein when executed by the processing circuit 301. In another example, the functionality of any of such components may be divided between the processing circuit 301 and the communication subsystem 331. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0072] Figure 4 400 is a schematic block diagram of a virtualized environment 400, in which the functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or device, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and involves at least a portion of the functionality (e.g., one or more applications, components, functions, virtual machines, or containers executed via one or more physical processing nodes in one or more networks) being implemented as an implementation of one or more virtual components.

[0073] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 400 hosted by one or more of the hardware nodes 430. Additionally, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), then the network nodes may be fully virtualized.

[0074] These functions may be implemented by one or more applications 420 (alternatively they may be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. The applications 420 run in a virtualized environment 400, which provides hardware 430 including processing circuitry 460 and memory 490. The memory 490 contains instructions 495 executable by the processing circuitry 460, whereby the applications 420 are operable to provide one or more of the features, benefits, and / or functions disclosed herein.

[0075] The virtualized environment 400 includes a general or special purpose network hardware device 430, which includes a collection of one or more processors or processing circuits 460, which may be commercial off-the-shelf (COTS) processors, specialized application-specific integrated circuits (ASICs), or any other type of processing circuit, including digital or analog hardware components or special purpose processors. Each hardware device may include a memory 490-1, which may be a non-persistent memory for temporarily storing software or instructions 495 executed by the processing circuit 460. Each hardware device may include one or more network interface controllers (NICs) 470, also known as network interface cards, which include physical network interfaces 480. Each hardware device may also include a non-transitory, permanent machine-readable storage medium 490-2 in which instructions and / or software 495 executable by the processing circuit 460 are stored. The software 495 may include any type of software, including software for instantiating one or more virtualization layers 450 (also known as hypervisors), software for executing virtual machines 440, and software that allows them to perform the functions, features, and / or benefits described in conjunction with some of the embodiments described herein.

[0076] The virtual machine 440 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 450 or hypervisor. Different embodiments of the instance of the virtual device 420 can be implemented on one or more of the virtual machines 440, and the implementation can be performed in different ways.

[0077] During operation, processing circuitry 460 executes software 495 to instantiate a hypervisor or virtualization layer 450, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 450 may present to virtual machines 440 a virtual operating platform that appears to be networked hardware.

[0078] like Figure 4As shown, hardware 430 can be an independent network node with common or specific components. Hardware 430 can include antenna 425, and some functions can be implemented via virtualization. Alternatively, hardware 430 can be part of a larger hardware cluster (e.g., such as in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed via management and orchestration (MANO) 410, which also oversees the life cycle management of application 420.

[0079] Hardware virtualization is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switching equipment, and physical storage devices, which can be located in data centers and customer premises equipment.

[0080] In the context of NFV, virtual machines 440 may be software implementations of physical machines that run programs as if they were executing on a physical, non-virtualized machine. Each of the virtual machines 440 and the portion of the hardware 430 that executes the virtual machine, if it is hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 440, forms a separate virtual network element (VNE).

[0081] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 440 atop the hardware networking infrastructure 430 and corresponds to Figure 4 Application 420.

[0082] In some embodiments, one or more radio units 420, each including one or more transmitters 422 and one or more receivers 421, may be coupled to one or more antennas 425. Radio units 420 may communicate directly with hardware nodes 430 via one or more appropriate network interfaces, and may be used in combination with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations.

[0083] In some embodiments, some signaling may be accomplished using a control system 4230 , which may alternatively be used for communications between the hardware node 430 and the radio unit 4200 .

[0084] refer to Figure 5According to an embodiment, a communication system includes a telecommunication network 510, such as a 3GPP type cellular network, which includes an access network 511 (such as a radio access network) and a core network 514. The access network 511 includes a plurality of base stations 512a, 512b, 512c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 513a, 513b, 513c. Each base station 512a, 512b, 512c may be connected to the core network 514 via a wired or wireless connection 515. A first UE 591 located in the coverage area 513c is configured to be wirelessly connected to the corresponding base station 512c, or to be paged by the corresponding base station 512c. A second UE 592 in the coverage area 513a may be wirelessly connected to the corresponding base station 512a. Although multiple UEs 591, 592 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connecting to the corresponding base station 512.

[0085] The telecommunications network 510 itself is connected to a host computer 530, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 530 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. Connections 521 and 522 between the telecommunications network 510 and the host computer 530 may extend directly from the core network 514 to the host computer 530, or may be via an optional intermediate network 520. The intermediate network 520 may be one or a combination of more than one of a public, private, or hosted network; the intermediate network 520, if any, may be a backbone network or the Internet; in particular, the intermediate network 520 may include two or more subnets (not shown).

[0086] Figure 5The communication system as a whole implements connectivity between the connected UEs 591, 592 and the host computer 530. This connectivity can be described as an over-the-top (OTT) connection 550. The host computer 530 and the connected UEs 591, 592 are configured to use the access network 511, the core network 514, any intermediate networks 520 and possible additional infrastructure (not shown) as intermediaries to pass data and / or signaling via the OTT connection 550. The OTT connection 550 can be transparent in the sense that the participating communication devices through which the OTT connection 550 passes do not know the routes of uplink and downlink communications. For example, the base station 512 may not be informed or need not be informed of the past routes of incoming downlink communications, where data originating from the host computer 530 is to be forwarded (e.g., handed over) to the connected UE 591. Similarly, the base station 512 does not need to know the future routes of outgoing uplink communications originating from the UE 591 toward the host computer 530.

[0087] According to the embodiment, reference will now be made to Figure 6 Describe the example implementation of the UE, base station and host computer discussed in the previous paragraph. In the communication system 600, the host computer 610 includes hardware 615, which includes a communication interface 616, which is configured to establish and maintain a wired or wireless connection of the interface of different communication devices of the communication system 600. The host computer 610 further includes a processing circuit 618, which may have storage and / or processing capabilities. In particular, the processing circuit 618 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 610 further includes software 611, which is stored in the host computer 610 or accessible by the host computer 610 and executable by the processing circuit 1918. The software 611 includes a host application 612. The host application 612 may be operable to provide services to remote users, such as UE 630 connected via an OTT connection 650 terminating at the UE 630 and the host computer 610. In providing services to remote users, the host application 612 may provide user data transmitted using the OTT connection 650 .

[0088] The communication system 600 further includes a base station 620, which is provided in the telecommunication system and includes hardware 625, enabling it to communicate with the host computer 610 and the UE 630. The hardware 625 may include a communication interface 626 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 600, and for establishing and maintaining connections with the base stations located in the coverage area ( Figure 6The communication interface 626 may be configured to facilitate a connection 660 to the host computer 610. The connection 660 may be direct, or it may be through a core network (eg, a wireless network) of the telecommunications system. Figure 6 ) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 625 of the base station 620 further includes processing circuitry 628, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The base station 620 further has software 621 stored internally or accessible via an external connection.

[0089] The communication system 600 also includes the UE 630 already mentioned. Its hardware 635 may include a radio interface 637, which is configured to establish and maintain a wireless connection 670 with a base station serving the coverage area where the UE 630 is currently located. The hardware 635 of the UE 630 can also include a processing circuit 638, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 630 also includes software 631, which is stored in the UE 630 or accessible by the UE 630 and executable by the processing circuit 638. The software 631 includes a client application 632. The client application 632 may be operable to provide services to human or non-human users via the UE 630 with the support of the host computer 610. In the host computer 610, the executing host application 612 can communicate with the executing client application 632 via an OTT connection 650 terminated at the UE 630 and the host computer 610. When providing services to users, client application 632 can receive request data from host application 612 and provide user data in response to the request data. OTT connection 650 can transmit both request data and user data. Client application 632 can interact with the user to generate the user data it provides.

[0090] Notice, Figure 6 The host computer 610, base station 620 and UE 630 shown may be similar to or identical to Figure 5 The host computer 530, one of the base stations 512a, 512b, 512c and one of the UEs 591, 592. That is, the internal workings of these entities can be as follows Figure 6 shown, and independently, the surrounding network topology can be Figure 5 network topology.

[0091] exist Figure 6In the figure, OTT connection 650 has been abstractly drawn to illustrate communication between host computer 610 and UE 630 via base station 620, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the route, which can be configured to hide the route from UE 630 or the service provider operating host computer 610, or both. When OTT connection 650 is active, the network infrastructure can further make decisions by which it dynamically changes the route (e.g., based on network reconfiguration or load balancing considerations).

[0092] The wireless connection 670 between the UE 630 and the base station 620 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of an OTT service provided to the UE 630 using the OTT connection 650, wherein the wireless connection 670 forms the last leg. More specifically, the teachings of these embodiments can improve the handling of connection errors, the delivery of error information, and thereby provide benefits such as improved speed of connection and reduced chance of subsequent message rejection.

[0093] A measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. There may also be optional network functionality for reconfiguring the OTT connection 650 between the host computer 610 and the UE 630 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 650 may be implemented in the software 611 and hardware 615 of the host computer 610 or in the software 631 and hardware 635 of the UE 630 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 650 passes; the sensor may participate in the measurement process by providing the values ​​of the monitored quantities exemplified above or by providing the values ​​of other physical quantities from which the software 611, 631 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 650 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 620 and may be unknown or imperceptible to the base station 620. Such processes and functionality may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling, thereby facilitating host computer 610 measurements of throughput, propagation time, latency, etc. The measurements may be accomplished by software 611 and 631 causing a message, particularly a null or "dummy" message, to be transmitted using OTT connection 650 while it monitors propagation time, errors, etc.

[0094] Figure 7is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 5 and 6 To simplify this disclosure, only the Figure 7 . In step 710, the host computer provides user data. In sub-step 711 of step 710 (which may be optional), the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission that carries the user data to the UE. In step 730 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0095] Figure 8 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 5 and 6 To simplify this disclosure, only the Figure 8 . In step 810 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 820, the host computer initiates a transmission that carries the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through a base station. In step 830 (which may be optional), the UE receives the user data carried in the transmission.

[0096] Fig. 9 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 5 and 6 To simplify this disclosure, only the Fig. 9. In step 910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 920, the UE provides user data. In sub-step 921 of step 920 (which may be optional), the UE provides user data by executing a client application. In sub-step 911 of step 910 (which may be optional), the UE reacts to the received input data provided by the host computer and executes the client application that provides user data. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, in sub-step 930 (which may be optional), the UE initiates transmission of the user data to the host computer. In step 940 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data transmitted from the UE.

[0097] Fig.10 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 5 and 6 To simplify this disclosure, only the Fig.10 In step 1010 (which may be optional), according to the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In step 1020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0098] Fig.11 Methods according to certain embodiments are described. Fig.11The method shown is performed by a core network node, such as a mobility management entity (MME). The method starts at step 1102, where a retrieve UE information message is received from a base station (e.g., an eNB). The retrieved UE information may include identification information of a wireless device, which is not an APID of the wireless device, for example, the identification information may be a temporary identifier of the wireless device, such as an S-TMSI. The method may also include, at step 1104, initiating transmission of an error indication message to the base station. The error indication message may include identification information of a wireless device, which is the source of the incoming message for which the error was detected; the identification information may be the same as the identification information included in the retrieve UE information message when step 1102 has been performed. The identification information may not be an APID, but may be (for example) an S-TMSI, a 5G-S-TMSI, an IMSI, etc. The method may also include, at step 1106, receiving an initial UE message from the base station. The initial UE message may omit identification information of a wireless device that has been indicated (by the error indication message) as unknown to the core network node.

[0099] Fig.12 Methods according to certain embodiments are described. Fig.12 The method shown is performed by a base station, such as an eNB. The method starts at step 1202, where a UE information transfer message is received from a core network node (e.g., an MME). The UE information transfer message may include identification information of a wireless device, which is not an APID of the wireless device. For example, the identification information may be a temporary identification of the wireless device, such as an S-TMSI. The method may also include, at step 1204, initiating transmission of an error indication message to the core network node. The error indication message may include identification information of a wireless device, which is the source of the incoming message where the error is detected; the identification information may be the same as the identification information included in the UE information transfer message when performing step 1202. The identification information may not be an APID, but may be (for example) an S-TMSI, a 5G-S-TMSI, an IMSI, etc. The method may also include, at step 1206, receiving an additional message from the core network node. The additional message may omit the identification information of the wireless device that has been indicated as unknown to the base station (via the error indication message).

[0100] Fig.13 A wireless network (e.g., Figure 2 1300 in a wireless network). The device may be in a wireless device or a network node (e.g., Figure 2 The apparatus 1300 is implemented in the wireless device 210 or the network node 260 shown in FIG. Fig.11 The example methods described herein and any other processes or methods that may be disclosed herein. It should also be understood that Fig.11The method is not necessarily performed only by the device 1300. At least some operations of the method may be performed by one or more other entities.

[0101] The virtual device 1300 may include processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuitry may be configured to execute program code stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some embodiments, the processing circuitry may be used to cause the processing unit 1302 to process information, in particular to process information in a message received from another node (e.g., a base station) via the transmission / reception unit 1304, and according to one or more embodiments of the present disclosure, cause the transmission / reception unit 1304 to transmit or initiate a transmission to another node as described above, and any other suitable unit of the device 1300 performs a corresponding function.

[0102] Fig.14 A wireless network (e.g., Figure 2 Schematic block diagram of a virtual core network node device 1400 in a wireless network (shown in FIG. 1 ). The device may be configured to be operable at one or more base stations (e.g., Figure 2 The device 1400 is operable to perform the reference Fig.12 The example methods described herein and any other processes or methods that may be disclosed herein. It should also be understood that Fig.12 The method is not necessarily performed only by the device 1400. At least some operations of the method may be performed by one or more other entities.

[0103] The virtual device 1400 may include a processing circuit, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, the processing circuit may be used to cause the processing unit 1402 to process information, in particular, to process information in a message received from another node (e.g., a base station) via the transmission / reception unit 1404, and according to one or more embodiments of the present disclosure, cause the transmission / reception unit 1404 to transmit or initiate a transmission to another node as described above, and any other suitable unit of the device 1400 performs a corresponding function.

[0104] The term "unit" has a conventional meaning in the field of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., such as those described herein.

[0105] The following numbered statements provide additional information about certain aspects of the embodiments.

[0106] 1. A method for sharing error information performed by a core network node, the method comprising: - initiating the transmission of an error indication message to a base station connected to said core network node, The error indication message includes identification information of a wireless device that is a source of an incoming message for which an error has been detected.

[0107] 2. The method of statement 1, wherein the identification information of the wireless device comprises a temporary identifier of the wireless device.

[0108] 3. The method of statement 2, wherein the temporary identifier is unique within a plurality of wireless devices served by the core network node.

[0109] 4. A method according to statement 3, wherein the core network node is a mobility management entity (MME).

[0110] 5. A method according to any of the preceding statements, wherein the error indication message includes a UE identity element.

[0111] 6. A method according to statement 5, wherein the UE identity element specifies whether one or more UE identity formats are used in the error indication message.

[0112] 7. A method according to statement 6, wherein the UE identity element specifies whether one or more UE identity formats are to be used with a numeric reference of the UE identity format, or wherein the UE identity formats are listed.

[0113] 8. A method according to any of the preceding statements, wherein the identification information comprises at least one of the following: System architecture evolution Temporary Mobile Subscriber Identifier S-TMSI; 5G-S-TMSI; and International Mobile Subscriber Identifier IMSI.

[0114] 9. A method according to any of the preceding statements, wherein the core network node initiates transmission of the error indication message to the base station in response to a retrieve UE information message received from the base station.

[0115] 10. A method according to statement 9, wherein the retrieved UE information message includes identification information of the wireless device, the wireless device is the source of the incoming message that has detected the error in a given UE identity format, and wherein the error indication message includes identification information of the wireless device, the wireless device is the source of the incoming message that has detected the error in the same given UE identity format.

[0116] 11. A method according to any of the preceding statements, wherein the core network node and the base station use S1 Application Protocol S1AP or NG Application Protocol NGAP.

[0117] 12. The method of any of the preceding statements, wherein the error indication message does not include an APID of the wireless device.

[0118] 13. A method for sharing error information performed by a base station, the method comprising: - initiating the transmission of an error indication message to a core network node connected to said base station, The error indication message includes identification information of a wireless device that is a source of an incoming message for which an error has been detected.

[0119] 14. A method according to statement 13, wherein the identification information of the wireless device includes a temporary identifier of the wireless device.

[0120] 15. A method according to statement 14, wherein the temporary identifier is unique within a plurality of wireless devices served by the core network node, and wherein the core network node is a mobility management entity (MME).

[0121] 16. A method according to any of statements 13 to 15, wherein the base station is an eNB.

[0122] 17. A method according to any of statements 13 to 16, wherein the error indication message includes a UE identity element.

[0123] 18. A method according to statement 17, wherein the UE identity element specifies whether one or more UE identity formats are used in the error indication message.

[0124] 19. A method according to statement 18, wherein the UE identity element specifies whether one or more UE identity formats are to be used with a numeric reference of the UE identity format, or wherein the UE identity formats are listed.

[0125] 20. A method according to any one of statements 13 to 20, wherein the identification information comprises at least one of the following: System architecture evolution Temporary Mobile Subscriber Identifier S-TMSI; 5G-S-TMSI; and International Mobile Subscriber Identifier IMSI.

[0126] 21. A method according to any one of statements 13 to 20, wherein the base station initiates transmission of the error indication message to the core network node in response to a UE information transfer message received from the core network node.

[0127] 22. A method according to statement 21, wherein the retrieved UE information message includes identification information of the wireless device, the wireless device is the source of the incoming message that has detected the error in a given UE identity format, and wherein the error indication message includes identification information of the wireless device, the wireless device is the source of the incoming message that has detected the error in the same given UE identity format.

[0128] 23. A method according to any one of statements 13 to 22, wherein the core network node and the base station use S1 application protocol S1AP or NG application protocol NGAP.

[0129] 24. A method according to any of statements 13 to 23, wherein the error indication message does not include an APID of the wireless device.

[0130] 25. A method according to any one of statements 13 to 24, further comprising: configuring, by the base station, a subsequent message sent to the core network node based on the information in the error indication message.

[0131] 26. A method according to statement 25, wherein if the error indication message indicates that the core network node is not aware of a given UE ID in a given UE identity format, the base station may configure subsequent messages to omit the given UE ID.

[0132] 27. A core network node for sharing error information, the core network node comprising: - processing circuitry configured to perform any of the steps of any of statements 1 to 12; and - A power supply circuit configured to supply power to the core network node.

[0133] 28. A base station for sharing error information, the base station comprising: - processing circuitry configured to perform any of the steps of any of statements 13 to 26; - A power supply circuit configured to supply power to the base station.

[0134] 29. A core network node for sharing error information, the core network node comprising: - an antenna configured to send and receive wireless signals; - a radio front end circuit coupled to the antenna and the processing circuit and configured to condition signals passed between the antenna and the processing circuit; - a processing circuit configured to perform any of the steps of any of statements 1 to 12; - an input interface connected to the processing circuitry and configured to allow information to be input into the core network node for processing by the processing circuitry; - an output interface connected to the processing circuit and configured to output information from the core network node that has been processed by the processing circuit; and - A power supply connected to the processing circuitry and configured to supply power to the core network node.

[0135] 30. A communication system including a host, comprising: - processing circuitry configured to provide user data; and - a communication interface configured to forward the user data to a cellular network for transmission to the wireless device, - wherein the cellular network comprises a base station having a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any of the steps of any of statements 13 to 26.

[0136] 31. A communication system according to statement 30, further comprising a base station.

[0137] 32. A communication system according to any of statements 30 and 31, further comprising a wireless device, wherein the wireless device is configured to communicate with the base station.

[0138] 33. A communication system according to any one of statements 30 to 32, wherein: - the processing circuitry of the host is configured to execute a host application to provide user data; and - The wireless device comprises a processing circuit configured to execute a client application associated with a host application.

[0139] 34. A method implemented in a communication system comprising a host computer, a base station and a wireless device, the method comprising: - at the host computer, providing user data; and - at a host computer, initiating a transmission carrying user data to a wireless device via a cellular network comprising a base station, wherein the base station performs any of the steps of any of statements 13 to 26.

[0140] 35. A method according to statement 34, further comprising transmitting user data at the base station.

[0141] 36. A method according to any of statements 34 and 35, wherein the user data is provided at the host computer by executing a host application, the method further comprising executing a client application associated with the host application at the wireless device.

[0142] 37. A communication system including a host computer, comprising: - processing circuitry configured to provide user data; and - a communication interface configured to forward user data to a cellular network for transmission using a core network node, - wherein the core network node comprises a radio interface and a processing circuit, the components of the core network node being configured to perform any of the steps of any of statements 1 to 12.

[0143] 38. A communication system according to statement 37, wherein the cellular network further comprises a base station configured to communicate with the core network node.

[0144] 39. A communication system according to any one of statements 37 and 38, wherein: - the processing circuit of the host computer is configured to execute a host application program, thereby providing user data; and - the communication system further comprises a wireless device, the processing circuit of the wireless device being configured to execute a client application associated with the host application.

[0145] 40. A method implemented in a communication system including a host computer, a base station, and a wireless device, the method comprising: - at the host computer, providing user data; and - at a host computer, initiating a transmission carrying user data to a wireless device via a cellular network comprising a base station, wherein the base station performs any of the steps of any of statements 13 to 26.

[0146] 41. A method as recited in the preceding statement, further comprising, at the UE, receiving user data from a base station.

[0147] 42. A communication system including a host computer, comprising: - A communication interface configured to receive user data originating from a transmission from a wireless device to a base station, wherein the base station comprises a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any of the steps of any of statements 13 to 26.

[0148] 43. A communications system according to statement 42, further comprising a UE, wherein the UE comprises a radio interface and a processing circuit.

[0149] 44. The communication system according to any one of statements 42 and 43 further includes the base station, wherein the base station includes a radio interface configured to communicate with the wireless device and a communication interface, which is configured to forward user data carried by the transmission from the wireless device to the base station to the host computer.

[0150] 45. A communication system according to any one of statements 42 to 44, wherein: - the processing circuitry of the host computer is configured to execute a host application; and - The processing circuitry of the wireless device is configured to execute a client application associated with the host application, thereby providing user data.

[0151] 46. ​​A communication system according to any one of statements 42 to 45, wherein: - the processing circuitry of the host is configured to execute a host application to provide the request data; and - the processing circuitry of the wireless device is configured to execute a client application associated with the host application to provide the user data in response to the request data.

[0152] 47. A method implemented in a communication system including a host computer, a base station, a core network node, and a wireless device, the method comprising: - At a core network node, receiving data transmitted from a base station to the core network node, wherein the core network node performs any of the steps of any of statements 1 to 13.

[0153] 48. The method of statement 47 further comprising a wireless device, wherein the wireless device provides user data to the base station.

[0154] 49. A method according to any one of statements 47 and 48, further comprising: - at the wireless device, executing a client application, thereby providing user data to be transmitted; and - at the host computer, executing a host application associated with the client application.

[0155] 50. A method according to any one of statements 47 to 49, further comprising: - at the wireless device, executing a client application; and - receiving, at the wireless device, input data from the client application, providing the input data at the host computer by executing a host application associated with the client application, - wherein user data to be transmitted is provided by a client application in response to input data.

[0156] 51. A communications system comprising a host computer, the host computer comprising a communications interface, the communications interface being configured to receive user data originating from a transmission from a core network node to a base station, wherein the base station comprises a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps in any of statements 13 to 26.

[0157] 52. A communication system according to statement 51, further comprising a base station.

[0158] 53. A communication system according to any of statements 51 and 52, further comprising a core network node, wherein the core network node is configured to communicate with the base station.

[0159] 54. A communication system according to any one of statements 51 to 53, wherein: - the processing circuitry of the host computer is configured to execute a host application; - The communication system further comprises a UE configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0160] 55. A method implemented in a communication system including a core network node, a base station and a wireless device, the method comprising: - receiving, at the core network node, from a base station user data originating from a transmission that the base station has received from the wireless device, wherein the base station performs any of the steps of any of statements 13 to 26.

[0161] 56. The method of statement 55 further comprising, at the base station, receiving user data from the wireless device.

[0162] 57. A method according to any one of statements 55 and 56, further comprising, at the base station, initiating transmission of the received user data to the core network node 58. A method according to any one of statements 55 to 57, wherein the core network node performs any of the steps of any one of statements 1 to 12.

[0163] abbreviation At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, the above usage shall take precedence. If listed multiple times below, the first listing shall take precedence over any subsequent listings: NG-RAN NG Radio Access Network NR New Radio 5G AMF access and mobility management function MME mobility management entity eNB Evolved Node B 1x RTT CDMA2000 1x wireless transmission technology 3GPP Third Generation Partnership Project 5G fifth generation ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC carrier component CCCH SDU Common Control Channel SDU CDMA Code Division Multiplexing Access CGI Cell Global Identifier CIR channel impulse response CP cyclic prefix CPICH common pilot channel CPICH Ec / No The energy received by each CPICH chip divided by the power density in the frequency band CQI channel quality information C-RNTICell RNTI CSI channel state information DCCH dedicated control channel DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell-ID (positioning method) E-SMLC Evolution - Service Mobile Location Center ECGI Evolution CGI ePDCCH enhanced physical downlink control channel E-SMLC Evolution Service Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved Universal Terrestrial Radio Access Network FDD Frequency Division Duplex FFS for further study GERAN GSM EDGE Radio Access Network Base stations in gNB NR GNSS Global Navigation Satellite System GSM Global System for Mobile Communications HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed ​​Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long Term Evolution MAC Media Access Control MBMS Multimedia Broadcast Multicast Service MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFNABS MBSFN Almost Blank Subframes MDT Minimization of Drive Test MIB Master Information Block MSC Mobile Switching Center NPDCCH narrowband physical downlink control channel OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operation Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDP Power Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid ARQ Indicator Channel PLMN Public Land Mobile Network PMI precoder matrix indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS primary synchronization signal PUCCH Physical uplink control channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS reference signal RSCP received signal code power RSRP reference symbol received power or reference signal received power RSRQ reference signal reception quality or reference symbol reception quality RSSI received signal strength indicator RSTD Reference Signal Time Difference RWR release via redirection SCH synchronization channel SCell secondary cell SDU Service Data Unit SFN system frame number SGW Service Gateway SI system information SIB System Information Block SNR signal-to-noise ratio SON Self-Optimizing Network SS sync signal SSS secondary synchronization signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Arrival Time TSS three-level synchronization signal TTI transmission time interval UE User Equipment UL Uplink UMTS Universal Mobile Telecommunications System USIM Universal User Identity Module UTDOA uplink time difference of arrival UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Broadband CDMA WLAN

Claims

1. A method for sharing error information performed by a core network node, the method comprising: - initiating the transmission of an error indication message to a base station connected to said core network node, The error indication message includes identification information of a wireless device that is a source of an incoming message for which an error has been detected.

2. The method according to claim 1, wherein: The identification information of the wireless device includes a temporary identifier of the wireless device.

3. The method according to claim 2, wherein: The temporary identifier is unique within a plurality of wireless devices served by the core network node.

4. The method according to claim 3, wherein: The core network node is a mobility management entity MME.

5. A method according to any one of the preceding claims, wherein: The error indication message includes a UE identity element.

6. The method according to claim 5, wherein: The UE identity element specifies whether one or more UE identity formats are used in the error indication message.

7. The method according to claim 6, wherein: The UE identity element specifies whether one or more UE identity formats are used together with a numeric reference of the UE identity format, or where the UE identity formats are listed.

8. A method according to any one of the preceding claims, wherein: The identification information includes at least one of the following: System architecture evolution Temporary Mobile Subscriber Identifier S-TMSI; 5G-S-TMSI; and International Mobile Subscriber Identifier IMSI.

9. A method according to any one of the preceding claims, wherein: The core network node initiates transmission of the error indication message to the base station in response to a retrieve UE information message received from the base station.

10. The method according to claim 9, wherein: The retrieve UE information message includes identification information of the wireless device, which is the source of the incoming message that has detected the error in a given UE identity format, and wherein the error indication message includes identification information of the wireless device, which is the source of the incoming message that has detected the error in the same given UE identity format.

Images