Event reporting method and device

Abstract

The embodiment of the invention provides an event reporting method and device. A method performed by a source AMF may include determining that a UE context containing event subscription information should be transmitted to a target AMF during an AMF relocation procedure. The method may also include sending event subscription information to the target AMF indicating when to send the next event cycle report to the network function service consumer.

Description

Technical Field

[0001] Non-limiting and exemplary embodiments of the present disclosure relate generally to the field of communication technology, and in particular to methods and apparatus for event reporting. background

[0002] This section introduces aspects that may help to better understand the present disclosure. Therefore, the statements in this section should be read in this light and should not be understood as an admission of what is or is not prior art.

[0003] Network capability opening may include various network capability openings. For example, network capability opening may include opening network events to the inside and outside of the core network NF, opening configuration capabilities to external functions, opening policies and charging capabilities to external functions, opening analysis capabilities within the core network, opening analysis to external parties, retrieving data from external parties through a network data analysis function (NWDAF), opening the number of registered user equipment (UE) and / or established protocol data units (PDUs) for network slices subject to network slice admission control pointing to a core network (CN) network function (NF) or external, etc.

[0004] When subscribing to an event report, a NF consumer can provide various information. For example, a NF consumer can provide the following information:

[0005] - One or more event identifiers (IDs). The event ID identifies the event type subscribed to (e.g., PDU session release, UE mobility out of area of ​​interest, etc.).

[0006] -Event filter information: Provides the event parameter type and event parameter value to be matched to satisfy the conditions of the notification subscription event ID, for example, the event parameter type can be "area of ​​interest" and the event parameter value list can be a list of tracking areas (TAs); the event filter depends on the event ID. Event filter information is provided per subscribed event ID: in a subscription, different event IDs may be associated with different event filter information.

[0007] - Event report information. In a subscription, all event IDs are associated with unique event report information.

[0008] - Event Report Target: This may indicate a specific UE or PDU Session, a group of UEs, or any UE (i.e. all UEs). Within a subscription, all event IDs are associated with the same event reporting target (which may correspond to multiple UEs or multiple PDU Sessions).

[0009] - Notification Target Address (+Notification Correlation ID) allows the event receiving NF to associate notifications received from the event provider with this subscription. A subscription is associated with a unique Notification Target Address (+Notification Correlation ID). If a NF Consumer subscribes to an NF Producer on behalf of other NFs, the NF Consumer includes the Notification Target Address (+Notification Correlation ID) of the other NF in the Event IDs to be notified directly to the other NF and includes its own Notification Target Address (+Notification Correlation ID) in the subscription change related event notifications. Each Notification Target Address (+Notification Correlation ID) is associated with a related (set of) Event IDs.

[0010] - Expiration time indicates that the time for which you want the subscription to remain valid has expired. The NF Service Consumer can suggest an expiration time and provide it to the NF Service Producer. Based on the operator's policy, the NF Service Producer decides whether the subscription can expire. If the subscription can expire, the NF Service Producer determines the expiration time and provides it to the NF Service Consumer in the response. If the subscription is about to expire according to the received expiration time event and the NF Service Consumer wants to continue receiving notifications, the NF Service Consumer updates the subscription with the NF Service Producer to extend the expiration time. Once the expiration time associated with the subscription is reached, the subscription will become invalid at the NF Service Producer. If the NF Service Consumer wants to continue receiving notifications, it should create a new subscription with the NF Service Producer.

[0011] When the event provider NF accepts a subscription, the consumer NF can receive an identifier (subscription correlation ID) from the event provider NF in order to further manage (modify, delete) this subscription.

[0012] The notification correlation ID is assigned by the consumer NF that subscribes to the event report, while the subscription correlation ID is assigned by the NF that issues the notification when the event occurs. Both correlation identifiers can be assigned the same value, although in principle they should be different because they are optimized for finding the subscription related context in each NF.

[0013] The consumer NF can use operations dedicated to subscription modification to add or remove event IDs from this subscription, or to modify event filter information.

[0014] Consumer NF subscribes to events by providing event filters. The content of event report information and the existence requirements of each information element are described below.

[0015] For example, incident report information may include the following information:

[0016] - Event reporting mode, e.g., reporting with maximum number of reports, periodic reporting and periodic reporting, maximum duration of reporting, reporting when threshold is reached,

[0017] - maximum number of reports, i.e. the maximum number of reports after which the event subscription ceases to exist,

[0018] - the maximum duration reported, i.e. the maximum duration that an event subscription ceases to exist,

[0019] - Immediate reporting flag, i.e. the event provider NF immediately informs the consumer NF of the current status of the subscribed event (if available),

[0020] - sampling rate, e.g., the sampling percentage of user devices affected (1% .. 100%),

[0021] - Division criteria, e.g., criteria for dividing UEs before applying the sampling rate,

[0022] - Group Report Guard Time, e.g. a group-based monitoring configuration parameter indicating how long monitoring event reports related to UEs in the group may be aggregated before these reports are sent to the consumer NF,

[0023] - deactivate notification flag, which may indicate to the event provider NF that notifications of available events should be muted until the event consumer NF provides the retrieve notification flag to retrieve the stored events,

[0024] - retrieve notification flag which may instruct the event provider NF to send stored event notifications to the event consumer NF and again mute notifications of future events,

[0025] - the granularity of the dynamics, e.g. the maximum dynamic amount in an event that allows skipping of event notifications,

[0026] - the type of report, e.g. the event provider NF reports only if the event is different from a previously notified event,

[0027] - Reporting threshold, eg, the threshold indicates a level condition to be reached for reporting.

[0028] Flowchart of Namf_EventExposure_Subscribe and Notify operations according to an embodiment of the present disclosure.

[0029] NFs can use this program to subscribe to notifications.

[0030] As a NF service producer, AMF can subscribe to event open services. When the conditions defined in the event subscription are met, AMF can trigger event notifications to NF service consumers.

[0031] If the AMF receives an open subscription for an event with periodic reporting, the AMF shall report the event notification to the NF Service Consumer periodically according to the duration specified by the NF Service Consumer.

[0032] In step 1, an NF service consumer (e.g., Network Exposure Function (NEF) / Unified Data Management (UDM)) sends a request to subscribe to a set of event IDs in the Access and Mobility Management Function (AMF) in a Namf_EventExposure_Subscribe request. The NF service consumer can be the same NF (i.e., event receiving NF) that subscribes to receive event notification reports, or it can be a different NF. The NF service consumer subscribes to one or more events (identified by event IDs) and provides the associated notification endpoint of the event receiving NF. If the NF service consumer itself is not an event receiving NF, the NF service consumer should provide its own notification endpoint in addition to the notification endpoint of the event receiving NF. Each notification endpoint is associated with a related set of event IDs. This is to ensure that the NF service consumer can receive notifications of subscription change related events (e.g., subscription association ID changes).

[0033] The event report information defines the type of report requested. If the report event subscription is authorized by AMF, AMF will record the association between the event trigger and the requester identity.

[0034] For example, the trigger can be set to periodic and the reporting period (repPeriod) is present in the Namf_EventExposure_Subscribe request.

[0035] In step 2, AMF confirms the execution reply of Namf_EventExposure_Subscribe. AMF may start a timer based on repPeriod.

[0036] Step 3. When the timer expires, the AMF may send an event report request via Namf_EventExposure_Notify to the notification endpoint of the event receiving NF.

[0037] In step 4, the AMF may receive a Namf_EventExposure_Notification response from the notification endpoint of the event receiving NF.

[0038] If the subscription is still valid, the AMF may start the timer based on the repPeriod again and perform steps 3-4 again.

[0039] In addition, Sections 4.15.3.2.1, 4.15.3.2.2, and 4.15.3.2.3 of 3GPP TS 23.502 V17.5.0, the disclosure of which is incorporated herein by reference in its entirety, describe the information flows of Namf_EventExposure_Subscribe, unsubscribe and notify operations, Nudm_EventExposure_Subscribe, unsubscribe and notify operations, and Nnef_EventExposure_Subscribe, unsubscribe and notify operations. Summary of the invention

[0040] This Abstract is intended to introduce some concepts in a simplified form that are further described below in the Detailed Description. This Abstract is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0041] There are some problems with the existing solutions. For example, when a mobility process between NF service providers (e.g., AMF) occurs (e.g., mobility registration update with AMF relocation, or handover with AMF relocation), the source NF service provider (e.g., AMF) transfers the event subscription to the target NF service provider (e.g., AMF). However, the information indicating when the next report should be sent is not transmitted to the target NF service provider (e.g., AMF), and the target NF service provider (e.g., AMF) cannot correctly resume the periodic report because it does not know when the source NF service provider (e.g., AMF) performed the last report.

[0042] If the target NF service producer (such as AMF) decides to report immediately after receiving the event subscription from the source NF service producer (such as AMF), more event open notification messages may be reported to the NF service consumer as expected.

[0043] If the target NF service producer (e.g. AMF) decides to report after the repPeriod after receiving the event subscription from the source AMF, fewer event open notification messages may be reported to the NF service consumer as expected.

[0044] The situation will be even worse if the inter-NF service provider mobility process occurs frequently.

[0045] To overcome or mitigate at least one of the above-mentioned problems or other problems, an improved incident reporting solution is desirable.

[0046] In a first aspect of the present disclosure, a source access and mobility function (AMF) is provided. The method may include determining that a UE context containing event subscription information should be transferred to a target AMF during an AMF relocation process. The method may also include sending event subscription information to the target AMF, indicating the time of the next event period report to be sent to the network function service consumer.

[0047] In one embodiment, the event subscription information may include at least one of the following: a timestamp when a most recent event report is generated and notified to the network function service consumer, or a timestamp when a next event report is generated, or a calculated remaining time for a next event report.

[0048] In one embodiment, an event subscription may exist in an event subscription when the event subscription is transferred from the source AMF to the target AMF and the event trigger is set to periodic.

[0049] In one embodiment, an event subscription may include at least one of the following: a cycle time of event reporting, a maximum number of reports that can be generated for an event subscribed to in the event subscription, and a time when a subscribed event stops generating reports and the subscription becomes invalid.

[0050] In one embodiment, determining that the UE context including the event subscription information should be transferred to the target AMF may include receiving a message from a source Next Generation Radio Access Network (NG-RAN) node indicating that a handover is required.

[0051] In one embodiment, the method may further include receiving an event subscription request for an event report from a network function service consumer. The event subscription request may include event report information indicating that event reports should be sent periodically. The method may further include sending event reports to the network function service consumer based on a periodicity.

[0052] In one embodiment, the network function service consumer may include at least one of the following: a network exposure function (NEF), a session management function (SMF), a unified data management (UDM), a network data analysis function (NWDAF), an application function (AF), a location management function (LMF) or a gateway mobile location center (GMLC).

[0053] In one embodiment, the event subscription information may be sent to the target AMF in a mobility registration update with an AMF relocation procedure or in a handover with an AMF relocation procedure.

[0054] In a second aspect of the present disclosure, a method performed by a target access and mobility function (AMF) is provided. The method may include receiving event subscription information from a source AMF. The event subscription information may indicate when the next event periodic report is sent to a network function service consumer. The method may also include: sending the next event report to the network function service consumer based on the event subscription information.

[0055] In one embodiment, the event subscription information may include at least one of the following: a timestamp when the most recent event report is generated and notified to the network function service consumer, or a timestamp when the next event report is generated, or a calculated remaining time for the next event report.

[0056] In one embodiment, an event subscription may exist when an event subscription is transferred from a source AMF to a target AMF and an event trigger is set to periodic.

[0057] In one embodiment, an event subscription may include at least one of the following: a cycle time for event reporting, a maximum number of reports that can be generated for an event subscribed to in the event subscription, a time when a subscribed event stops generating reports, and a time when the subscription expires.

[0058] In one embodiment, the network function service consumer may include at least one of the following: network exposure function (NEF), session management function (SMF), unified data management (UDM), network data analysis function (NWDAF), application function (AF), location management function (LMF) or gateway mobile positioning center (GMLC).

[0059] In one embodiment, the event subscription information may be received from the source AMF in a mobility registration update with an AMF relocation procedure or in a handover with an AMF relocation procedure.

[0060] In one embodiment, sending the next event report to the network function service consumer based on the event subscription information may include: determining the remaining time of the started timer of the source AMF based on the event subscription information, when the remaining time is greater than zero, starting the timer based on the remaining time, and sending the next event report to the network function service consumer when the timer expires, and when the remaining time is equal to or less than zero, sending the next event report to the network function service consumer.

[0061] In a third aspect of the present disclosure, a source AMF is provided. The source AMF includes a processor and a memory coupled to the processor. The memory contains instructions executable by the processor. The source AMF can be used to determine that during the AMF relocation process, a UE context containing event subscription information should be transferred to a target AMF. The source AMF can also be used to send event subscription information to the target AMF, the event subscription information indicating the time when the next event period report is to be sent to the network function service consumer.

[0062] In a fourth aspect of the present disclosure, a target AMF is provided. The target AMF includes a processor and a memory coupled to the processor. The memory contains instructions executable by the processor. The target AMF can be used to receive event subscription information from the source AMF. The event subscription information can indicate the time when the next event periodic report is to be sent to the network function service consumer. The target AMF can also send the next event report to the network function service consumer based on the event subscription information.

[0063] In a fifth aspect of the present disclosure, a source AMF is provided. The source AMF includes a determination module configured to determine that a UE context containing event subscription information should be transferred to a target AMF during AMF relocation. The source AMF may also include a first sending module configured to send event subscription information to the target AMF, the event subscription information indicating the time when the next event period report is to be sent to the network function service consumer.

[0064] In one embodiment, the source AMF may further include a receiving module configured to receive an event subscription request for event reporting from a network function service consumer. The event subscription request may include event report information indicating that event reports should be sent periodically.

[0065] In one embodiment, the source AMF may also include a second sending module configured to send event reports to the network function service consumer based on a periodic basis.

[0066] In a sixth aspect of the present disclosure, a target AMF is provided. The target AMF includes a receiving module configured to receive event subscription information from a source AMF. The event subscription information indicates the time when the next event period report is to be sent to the network function service consumer. The target AMF also includes a sending module configured to send the next event report to the network function service consumer according to the event subscription information.

[0067] In another aspect of the present disclosure, a computer program product is provided, comprising instructions, which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first or second aspects.

[0068] In another aspect of the present disclosure, a computer-readable storage medium is provided, storing instructions, which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first or second aspects.

[0069] Embodiments herein may provide many advantages, and the following is a non-exhaustive list of examples. In some embodiments herein, even if mobility processes between network nodes (e.g., AMF) occur, periodic reports may be processed as expected. Changes in network nodes (e.g., AMF) cannot be perceived by NF service consumers. Embodiments herein are not limited to the above features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] The above and other aspects, features and advantages of various embodiments of the present disclosure will become more apparent through the following detailed description in conjunction with the accompanying drawings, in which the same reference numerals or letters are used to represent the same or equivalent elements. The accompanying drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein:

[0071] Figure 1 A flow chart of Namf_EventExposure_Subscribe and Notify operations is shown.

[0072] Figure 2 The high-level architecture in a fifth generation network according to an embodiment of the present disclosure is schematically shown;

[0073] Figure 3a A flowchart of a method according to an embodiment of the present disclosure is shown;

[0074] Figure 3b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0075] Figure 3c A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0076] Figure 4a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0077] Figure 4b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0078] Figure 5a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0079] Figure 5b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0080] Figure 6 A flow chart of a mobility registration update using AMF relocation according to an embodiment of the present disclosure is shown;

[0081] Figure 7 A flowchart of switching using an AMF relocation process according to an embodiment of the present disclosure is shown;

[0082] Figure 8a is a block diagram showing an embodiment suitable for practicing the present disclosure;

[0083] Figure 8b is a block diagram of a first network node according to an embodiment of the present disclosure;

[0084] Figure 8c is a block diagram illustrating a second network node according to an embodiment of the present disclosure;

[0085] Figure 8d is a block diagram illustrating a source AMF according to an embodiment of the present disclosure;

[0086] Figure 8e is a block diagram of an AMF according to an embodiment of the present disclosure;

[0087] Fig. 9 is a schematic diagram of a wireless network according to some embodiments;

[0088] Fig.10 is a schematic diagram of a user equipment according to some embodiments;

[0089] Fig.11 is a schematic diagram of a virtualization environment according to some embodiments;

[0090] Fig.12 is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0091] Fig.13 is a schematic diagram showing a host computer communicating with a user device via a base station through a partial wireless connection according to some embodiments;

[0092] Fig.14 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0093] Fig.15 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0094] Fig.16 is a schematic diagram showing a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments; and

[0095] Fig.17 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments. Specific embodiments

[0096] Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are only used to enable those skilled in the art to better understand and implement the present disclosure, rather than to impose any limitation on the scope of the present disclosure. The features, advantages or similar language cited in this specification does not mean that all functions and advantages that can be realized should be or exist in the present disclosure in any single embodiment. On the contrary, the language referring to features and advantages should be understood to mean that the features, advantages or characteristics of the specific description related to the embodiment are included in at least one embodiment of the present disclosure. In addition, the described features, advantages and characteristics of the present disclosure can be combined in one or more embodiments in any suitable manner. Those skilled in the relevant art will recognize that the present disclosure can be without the specific features or advantages of one or more specific embodiments. In other aspects, it can be recognized that the additional features and advantages in certain embodiments may not appear in all embodiments of the present disclosure.

[0097] The term "network" used herein refers to a network that follows any appropriate communication standard, such as new radio (NR), long term evolution (LTE), LTE-A (LTE-A), wideband code division multiple access (WCDMA), high speed packet access (HSPA), code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA) and other wireless networks. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA). UTRA includes other variants of WCDMA and CDMA. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802.20, Flash-OFDMA, Ad-hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" can be used interchangeably. Furthermore, communication between two devices in the network may be performed according to any suitable communication protocol, including but not limited to the communication protocol defined by IEEE 802.11. Standards organizations such as 3GPP. For example, the communication protocol may include first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols, and / or any other currently known or future developed protocol.

[0098] The term "network node" or "network entity" refers to any suitable network function (NF) that can be implemented in a network element (physical or virtual) of a communication network. For example, a network function can be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware, or a virtualized function instantiated on an appropriate platform, such as on a cloud infrastructure. For example, a 5G system (5GS) may include multiple NFs, such as AMF (Access and Mobility Management Function), SMF (Session Management Function), AU SF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User Plane Function) and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Agent), NWDAF (Network Data Analysis Function), NSSF (Network Slice Selection Function), NSSAAF (Network Slice Specific Authentication and Authorization Function), etc. For example, a 4G system (e.g., LTE) may include an MME (mobility management entity), an HSS (home subscriber server), a policy and charging rules function (PCRF), a packet data network gateway (PGW), a PGW control plane (PGW-C), a serving gateway (SGW), an SGW control plane (SGW-C), an E-UTRAN Node B (eNB), etc. In other embodiments, the network function may include different types of NFs, for example, depending on the specific network.

[0099] Virtualization means creating a virtual version of a device or apparatus, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization may be applied to provider edge nodes and refers to an implementation in which at least a portion of functionality is implemented as one or more virtual components (e.g., by one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0100] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments hosted by one or more hardware nodes. In addition, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity (e.g., core network nodes), provider edge nodes or PEs may be fully virtualized.

[0101] These functions may be implemented by one or more applications (also referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), which may be used to implement some features, functions, and / or advantages of some embodiments disclosed herein. The applications run in a virtualized environment that provides hardware including processing circuitry and memory. The memory contains instructions that can be executed by the processing circuitry, so the applications may be used to provide one or more features, advantages, and / or functions disclosed herein.

[0102] The virtualized environment includes a general or special-purpose network hardware device, including a set of one or more processors or processing circuits, which may be commercial off-the-shelf (COTS) processors, 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, which may be a non-persistent memory, for temporarily storing instructions or software executed by the processing circuit. Each hardware device may include one or more network interface controllers (NICs), also known as network interface cards, including physical network interfaces. Each hardware device may also include a non-temporary, persistent, machine-readable storage medium-storing software and / or instructions that can be executed by the processing circuit. The software may include any type of software, including software for instantiating one or more virtualization layers (also known as hypervisors), software for executing virtual machines, and software that allows it to perform functions, features, and / or advantages associated with some embodiments described herein.

[0103] A virtual machine includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer or hypervisor. Different embodiments of a virtual device instance can be implemented on one or more virtual machines, and the implementation can be different.

[0104] During operation, the processing circuitry executes software to instantiate a hypervisor or virtualization layer, sometimes referred to as a virtual machine monitor (VMM). The virtualization layer can present a virtual operating platform to the virtual machine that looks just like the network hardware.

[0105] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. As an example and not a limitation, a terminal device refers to a mobile terminal, a user equipment (UE) or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, an image capture terminal device (e.g., a digital camera), a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a notebook embedded device (LEE), a notebook mounted device (LME), a USB dongle, a smart device, a wireless client device (CPE), etc. In the following description, the terms "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured to communicate according to one or more communication standards issued by 3GPP (Third Generation Partnership Project), such as the LTE standard or the NR standard of 3GPP. As used herein, a "user equipment" or "UE" may not necessarily have a "user", i.e., a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human-computer interaction. For example, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to a request from a communication network. Conversely, a UE may represent a device that is intended to be sold to or operated by a human user, but may not be initially associated with a specific human user.

[0106] As another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the 3GPP context. As a specific example, a terminal device 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 (e.g., power meters), industrial machinery, or household or personal appliances, such as refrigerators, televisions, personal wearable devices (e.g., watches, etc.). In other scenarios, a terminal device may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0107] References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the embodiment may include certain features, structures, or characteristics, but not every embodiment necessarily includes the certain features, structures, or characteristics. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a certain feature, structure, or characteristic is described in conjunction with an embodiment, it should be recognized that those skilled in the art may affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0108] It should be understood that although the terms "first", "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the exemplary embodiments. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed terms.

[0109] As used herein, the phrase "at least one of A and B" or "at least one of A or B" should be understood as "only A, only B, or both A and B". The phrase "A and / or B" should be understood as "only A, only B, or both A and B".

[0110] The terms used herein are only used to describe specific embodiments and are not intended to limit the example embodiments. The singular forms "a", "an", and "the" used herein are also intended to include the plural forms, unless the context clearly indicates otherwise. It should be further understood that the terms "include", "comprise", "have", "include" and / or "comprising" used herein specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0111] It should be noted that the terms used in this article are only for the convenience of describing and distinguishing nodes, devices or networks, etc. As technology develops, other terms with similar / same meanings may also be used.

[0112] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0113] Although the subject matter described herein can be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a communication system. Figure 2 For simplicity, the system architecture Figure 2Only some exemplary elements are shown. In fact, the communication system may also include any additional elements suitable for supporting communication between terminal devices or between a wireless device and another communication device (such as a fixed telephone, a service provider, or any other network node or terminal device). The communication system can provide communication and various types of services to one or more terminal devices to facilitate the terminal devices to access and / or use services provided by or through the communication system.

[0114] Figure 2 The high-level architecture in the fifth generation network according to an embodiment of the present invention is schematically shown. For example, the fifth generation network may be 5GS. Figure 2 The architecture is the same as Figure 4.2.3-2 described in 3GPP TS 23.501 V17.5.0, the disclosure of which is incorporated herein by reference in its entirety. System Architecture Figure 2 Some example elements may be included, such as AUSF, AMF, DN (data network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP (service communication agent), NSSAAF (network slice specific authentication and authorization function), NSACF (network slice admission control function), etc.

[0115] According to an exemplary embodiment, the UE may establish a signaling connection with the AMF via reference point N1, such as Figure 2 As shown. The signaling connection can realize the NAS (non-access layer) signaling exchange between the UE and the AMF and the core network, including the signaling connection between the UE and the (R)AN and the UE and N2 connection used between the (R)AN and the AMF. The (R)AN can communicate with the UPF through the reference point N3. The UE can establish a protocol data unit (PDU) session with the DN (data network, such as an operator network or the Internet) through the UPF through the reference point N6.

[0116] like Figure 2 As shown, the exemplary system architecture also includes some reference points, such as N1, N2, N3, N4, N6, N9, N15, etc., which can support the interaction between NF services in NF. For example, these reference points can specify some NF service consumers and providers and their interactions through the corresponding NF service interface to perform specific system processes. PCF provides the AM-related policies of the registered UE to AMF through the N15 interface. AMF can obtain AM policies during the AM policy association establishment / modification process.

[0117] Figure 2The various NFs shown in the figure may be responsible for functions such as session management, mobility management, authentication, security, etc. AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, NSACF may include, for example, the functions defined in clause 6.2 of 3GPP TS 23.501 V17.5.0.

[0118] Figure 3a A flowchart of a method according to an embodiment of the present disclosure is shown, which can be implemented in a first network node or implemented as a first network node or communicatively coupled to a first network node by a device. Therefore, the device can provide a device or module for implementing each part of the method 300 and a means or module for completing other processes in combination with other components.

[0119] At 302, a first network node may determine an indication of when a next event report is to be sent to a network function service consumer.

[0120] The first network node may include a function that supports event opening. For example, the first network node may be AMF, UDM, PCF, NEF, SMF, AF, NSACF, UPF, etc., such as described in 3GPP TS 23.501 V17.5.0, the disclosure of which is incorporated herein by reference in its entirety. The corresponding event opening subscription, unsubscription and notification operations of these network functions are described in 3GPP TS 23.502 V17.5.0, the disclosure of which is incorporated herein by reference in its entirety.

[0121] The network function service consumer may be any suitable event receiving NF. In one embodiment, the network function service consumer includes at least one of the following: network open function (NEF), session management function (SMF), unified data management (UDM), network data analysis function (NWDAF), application function (AF), location management function (LMF), gateway mobile location center (GMLC) as described in 3GPP TS23.501V17.5.0.

[0122] The first network node may determine the information at any suitable point in time.In one embodiment, the first network node may determine the information for each event subscription for periodic reporting.

[0123] In one embodiment, the information includes at least one of the following: a timestamp of when the last event report was generated and notified to the network function service consumer, or a timestamp of a next event report, or a calculated remaining time for a next event report.

[0124] The first network node may receive an event open subscription request from a network function service consumer and confirm the execution of the event open subscription. Optionally, the first network node may detect the occurrence of a monitored event and send a time report to a notification endpoint of the event receiving NF via an event open notification message.

[0125] When the event trigger is set to "PERIODIC", a periodic time of event reporting may occur. In this case, the first network node can save the periodic time of event reporting and send the event report to the notification endpoint of the event receiving NF through the event open notification message. For example, if the periodicity of event reporting is 10 seconds, the first network node can send an event report to the notification endpoint of the event receiving NF through the event open notification message every 10 seconds.

[0126] In one embodiment, this information may be present in the event subscription when the event subscription is transmitted from the first network node to the second network node and the event trigger is set to be periodic.

[0127] An event subscription may include any appropriate information as described above. In one embodiment, an event subscription includes at least one of a periodic time for event reporting, a maximum number of reports that can be generated for an event subscribed to in the event subscription, and a time at which the subscribed event stops generating reports and the subscription expires. In one embodiment, an event subscription may include a periodic time for event reporting, and optionally a maximum number of reports and / or time.

[0128] For example, the periodicity time, maximum number of reports and time of event reporting may be the same as "maxReports", "expiry" and "repPeriod" described in clause 6.2.6.2.6 of 3GPP TS 29.518 v17.5.0, the disclosure of which is incorporated herein by reference in its entirety.

[0129] At 304, the first network node may send the information to the second network node.

[0130] The second network node may include functions required to support event open functions. For example, the second network node may be AMF, UDM, PCF, NEF, SMF, AF, NSACF, UPF, etc., as described in 3GPP TS 23.501 V17.5.0.

[0131] In one embodiment, the first network node is the source AMF and the second network node is the target AMF.

[0132] In one embodiment, the information is sent to the second network node in a mobility registration update with AMF relocation procedure or in a handover with AMF relocation procedure.

[0133] The information may be included in any suitable message, such as an existing message or a new message. For example, if the first and second network nodes are AMFs, the information may be included in a Namf_Communication_CreateUEContext request or a Namf_Communication_UEContextTransfer response, as described in 3GPP TS 23.502 V17.5.0.

[0134] Figure 3b A flow chart of a method according to an embodiment of the present disclosure is shown, which can be implemented in a source AMF or implemented as a source AMF or communicatively coupled to a source AMF by a device execution. Therefore, the device can provide a device or module for implementing various parts of the method 310 and a means or module for completing other processes in combination with other components.

[0135] At 312, the source AMF may determine that the UE context including the event subscription information should be transferred to the target AMF during the AMF relocation procedure.

[0136] In one embodiment, determining that the UE context including the event subscription information should be transferred to the target AMF may include receiving a message from a source Next Generation Radio Access Network (NG-RAN) node indicating that a handover is required.

[0137] At block 314, the source AMF may send to the target AMF event subscription information, indicating the time of the next event cycle report to be sent to the network function service consumer.

[0138] In one embodiment, the event subscription information may include at least one of the following: a timestamp of when the last event report was generated and notified to the network function service consumer, or a timestamp of the next event report, or a calculated remaining time for the next event report.

[0139] In one embodiment, an event subscription may exist in an event subscription when the event subscription is transmitted from the source AMF to the target AMF and the event trigger is set to periodic.

[0140] In one embodiment, an event subscription may include at least one of the following: a cycle time of event reporting, a maximum number of reports that can be generated for an event subscribed to in the event subscription, and a time when a subscribed event stops generating reports and the subscription becomes invalid.

[0141] In one embodiment, the network function service consumer may include a network exposure function (NEF), at least one of a session management function (SMF), a unified data management (UDM), a network data analysis function (NWDAF), an application function (AF), a location management function (LMF), or a gateway mobile location center (GMLC).

[0142] In one embodiment, the event subscription information may be sent to the target AMF in a mobility registration update with an AMF relocation procedure or in a handover with an AMF relocation procedure.

[0143] Figure 3c A flowchart of a method according to an embodiment of the present disclosure is shown, which can be implemented in a source AMF or implemented as a source AMF or communicatively coupled to a source AMF by a device. Therefore, the device can provide a device or module for implementing various parts of the method 320 and a means or module for completing other processes in combination with other components.

[0144] At 322, the source AMF may receive an event subscription request for an event report from a network function service consumer. The event subscription request may include event report information indicating that event reports should be sent periodically.

[0145] At 324, the source AMF may send an event report to the network function service consumer at a certain period.

[0146] Figure 4a A flowchart of a method according to another embodiment of the present disclosure is shown, which can be executed by a device or implemented as a second network node or communicatively coupled to a second network node. Therefore, the device can provide a device or module for implementing each part of the method 400 and a means or module for completing other processes in combination with other components.

[0147] At 402, the second network node may receive information from the first network node. The information indicates when the next event report is to be sent to the network function service consumer.

[0148] At 404, the second network node may send a next event report to the network function service consumer based on the information.

[0149] In one embodiment, the information includes at least one of the following: a timestamp of when the last event report was generated and notified to the network function service consumer, or a timestamp of a next event report, or a calculated remaining time for a next event report.

[0150] In one embodiment, the information is present in the event subscription when the event subscription is transmitted from the first network node to the second network node and the event trigger is set to be periodic.

[0151] In one embodiment, an event subscription includes at least one of the following: an event reporting cycle time, a maximum number of reports that can be generated for a subscribed event in the event subscription, or a time after which the subscribed event will stop generating reports and the subscription will become invalid.

[0152] In one embodiment, the first network node is the source AMF and the second network node is the target AMF.

[0153] In one embodiment, the network function service consumer includes at least one of the following: network exposure function (NEF), session management function (SMF), unified data management (UDM), network data analysis function (NWDAF), application function (AF), location management function (LMF), gateway mobile positioning center (GMLC).

[0154] In one embodiment, the information is received from the first network node in a mobility registration update with AMF relocation procedure or in a handover with AMF relocation procedure.

[0155] Figure 4a A flowchart of a method according to another embodiment of the present disclosure is shown, which can be implemented by a device executing on or as a target AMF or being communicatively coupled to a target AMF. Therefore, the device can provide a device or module for implementing various parts of the method 410 and a means or module for completing other processes in combination with other components.

[0156] At 412, the target AMF may receive event subscription information from the source AMF. The event subscription information indicates when the next event cycle report is to be sent to the network function service consumer.

[0157] At 414, the target AMF may send the next event report to the network function service consumer according to the event subscription information.

[0158] In one embodiment, the event subscription information may include at least one of the following: a timestamp of when the last event report was generated and notified to the network function service consumer, or a timestamp of the next event report, or a calculated remaining time for the next event report.

[0159] In one embodiment, an event subscription may exist when an event subscription is transferred from a source AMF to a target AMF and an event trigger is set to periodic.

[0160] In one embodiment, an event subscription may include at least one of the following: a cycle time for event reporting, a maximum number of reports that can be generated for an event subscribed to in the event subscription, a time when a subscribed event stops generating reports, and a time when the subscription expires.

[0161] In one embodiment, the network function service consumer may include a network exposure function (NEF), at least one of a session management function (SMF), a unified data management (UDM), a network data analysis function (NWDAF), an application function (AF), a location management function (LMF), or a gateway mobile location center (GMLC).

[0162] In one embodiment, the event subscription information may be received from the source AMF in a mobility registration update with an AMF relocation procedure or in a handover with an AMF relocation procedure.

[0163] Figure 5a A flowchart of a method according to another embodiment of the present disclosure is shown, which can be implemented by a device executed on or as a second network node or communicatively coupled to a second network node. Therefore, the device can provide a device or module for implementing each part of the method 500 and a means or module for completing other processes in combination with other components.

[0164] At 502, the second network node may receive information from the first network node. The information indicates when to send a next event report to the network function service consumer.

[0165] At 504, the second network node may determine a remaining time of a start timer of the first network node based on the information.

[0166] At 506 , when the remaining time is greater than zero, the second network node may start a timer based on the remaining time and send a next event report to the network function service consumer when the timer expires.

[0167] At 508 , when the remaining time is equal to or less than zero, the second network node may send a next event report to the network function service consumer.

[0168] Figure 5b A flowchart of a method according to another embodiment of the present disclosure is shown, which can be implemented by a device executing on or as a target AMF or being communicatively coupled to a target AMF. Therefore, the device can provide a device or module for implementing various parts of the method 510 and a means or module for completing other processes in combination with other components.

[0169] At 512, the target AMF may receive event subscription information from the source AMF. The event subscription information indicates when the next event cycle report will be sent to the network function service consumer.

[0170] At 514, the target AMF may determine the remaining time of the timer started by the source AMF according to the event subscription information.

[0171] At 516, when the remaining time is greater than zero, the target AMF may start a timer according to the remaining time and send a next event report to the network function service consumer when the timer expires.

[0172] At 518, when the remaining time is equal to or less than zero, the target AMF may send the next event report to the network function service consumer.

[0173] Figure 6 A flow chart of mobility registration update based on AMF relocation provided according to an embodiment of the present invention is shown.

[0174] In this embodiment, after the periodic event notification is reported, the source AMF updates lastReportTime to the timestamp of the last report, and the source AMF starts a new timer according to repPeriod.

[0175] In a Mobility Registration Update with AMF Relocation procedure, the source AMF may transmit repPeriod together with lastReportTime to the target AMF to resume periodic event reporting.

[0176] In step 1, the UE sends a registration request to the target AMF.

[0177] In step 2, the target AMF sends a Namf_Communication_UEContextTransfer request to the source AMF.

[0178] In step 3, the source AMF sends a Namf_Communication_UEContextTransfer request (eventSubscriptionList (repPeriod, lastReportTime for each event attribute of the periodic report) to the target AMF.

[0179] In step 4, optional: perform security procedures.

[0180] In step 5, the target AMF sends a Namf_Communication_RegistrationStatusUpdate request to the source AMF.

[0181] In step 6, the source AMF sends a Namf_Communication_RegistrationStatusUpdate response to the target AMF.

[0182] In step 7, the subscription data is retrieved and registered at the UDM.

[0183] In step 8, log out and cancel subscription on UDM

[0184] In step 9, the target AMF sends an Initial Context Setup Request to the NG-RAN (Next Generation RAN).

[0185] In step 10, the NG-RAN sends an Initial Context Setup Response to the target AMF.

[0186] In step 11, the target AMF sends a Nsmf_PDUSession_UpdateSMContext request or a Nsmf_PDUSession_ReleaseSMContext request to the SMF.

[0187] In step 12, the SMF sends a Nsmf_PDUSession_UpdateSMContext response or a Nsmf_PDUSession_ReleaseSMContext response to the target AMF.

[0188] In step 13, the target AMF sends a PDU session resource setup request to the NG-RAN.

[0189] In step 14, the target AMF sends a Registration Accept to the UE.

[0190] In step 15, the NG-RAN sends a PDU Session Resource Setup Response to the target AMF.

[0191] In step 16, the UE sends a Registration Complete to the target AMF.

[0192] If a periodic event subscription exists, the target AMF calculates the remaining time of the started timer from the source AMF and resumes the timer based on lastReportTime if maxReport and / or expiration time exist and are still valid.

[0193] For example, the algorithm might be as follows:

[0194] If lastReportTime+repPeriod>CurrentTime, then start the timer (reportTime+repPeriod-CurrentTime). Otherwise, the target AMF considers the timer expired and directly triggers the EventExposure notification.

[0195] CurrentTime is the current timestamp in the target AMF.

[0196] When the timer expires, steps 17 and 18 are performed.

[0197] In step 17, the target AMF sends a Namf_EventExposure notification request to the NEF.

[0198] In step 18, the NEF sends a Namf_EventExposure notification response to the target AMF.

[0199] Starts a new timer lastReportTime to the timestamp of the last report according to repPeriod and the target AMF updates if maxReport and / or expiration time exist and are still valid.

[0200] Figure 7 A flow chart is shown in which switching is performed using the AMF relocation process according to an embodiment of the present disclosure.

[0201] In this embodiment, after the periodic event notification is reported, the source AMF updates lastReportTime to the timestamp of the last report, and the source AMF starts a new timer according to repPeriod.

[0202] In a handover with AMF relocation procedure, the source AMF may transmit repPeriod together with lastReportTime to the target AMF to resume periodic event reporting.

[0203] In step 1, the source NG-RAN sends a Handover Required message to the source AMF.

[0204] In step 2, the source AMF sends a Namf_Communication_CreateUEContext request to the target AMF (event subscription list eventSubscriptionList (repPeriod for each event subscription for periodic reporting, lastReportTime for each active subscription for periodic reporting).

[0205] In step 3, the target AMF sends a Nsmf_PDUSession_UpdateSMContext request to the SMF.

[0206] In step 4, the SMF sends a Nsmf_PDUSession_UpdateSMContext response to the target AMF.

[0207] In step 5, the target AMF sends a handover request to the target NG-RAN.

[0208] In step 6, the target NG-RAN sends a Handover Request Acknowledgement to the target AMF.

[0209] In step 7, the target AMF sends a Nsmf_PDUSession_UpdateSMContext request to the SMF.

[0210] In step 8, the SMF sends a Nsmf_PDUSession_UpdateSMContext response to the target AMF.

[0211] In step 9, the target AMF sends a Namf_Communication_CreateUEContext response to the source AMF.

[0212] In step 10, the source AMF sends a handover command to the UE.

[0213] In step 11, the UE sends a handover confirmation to the target NG-RAN.

[0214] In step 12, the target NG-RAN sends a handover notification to the target AMF.

[0215] In step 13, the target AMF sends Namf_Communication_N2InfoNotify to the source AMF.

[0216] In step 14, the source AMF sends a Namf_Communication_N2InfoNotify confirmation to the target AMF.

[0217] In step 15, the target AMF sends a Nsmf_PDUSession_UpdateSMContext request to the SMF.

[0218] In step 16, the SMF sends a Nsmf_PDUSession_UpdateSMContext response to the target AMF.

[0219] In step 17, a mobile registration update procedure may be performed.

[0220] In step 18, the source AMF sends a UE context release command to the source NG-RAN.

[0221] In step 19, the source NG-RAN sends a UE context release complete to the source AMF.

[0222] If a periodic event subscription exists, the target AMF calculates the remaining time of the timer started by the source AMF and resumes the timer based on lastReportTime if maxReport and / or expiration time exist and are still valid.

[0223] For example, the algorithm might be as follows:

[0224] If lastReportTime+repPeriod>CurrentTime, the timer (reportTime+repPeriod-CurrentTime) is started. Otherwise, the target AMF considers that the timer has expired and directly triggers EventExposureNotify.

[0225] CurrentTime is the current timestamp in the target AMF.

[0226] When the timer expires, steps 20 and 21 are executed.

[0227] In step 20, the target AMF sends a Namf_EventExposure notification request to the NEF.

[0228] In step 21, the NEF sends a Namf_EventExposure notification response to the target AMF.

[0229] A new timer is started based on repPeriod and if maxReport and / or expiry time exist and are still valid, the target AMF updates lastReportTime to the timestamp of the last report.

[0230] Figure 6 to Figure 7 The message shown in may be the same as the corresponding message described in various 3GPP specifications (e.g., 3GPP TS 23.502 V17.5.0), except that the message sent from the source AMF to the target AMF may include information indicating when the next event report is sent to the network function service consumer.

[0231] According to various embodiments, the source network node (e.g., AMF) may include information to the target AMF to indicate when the next report should be sent to the network function service consumer. The information may be the timestamp of the last report, the timestamp of the next report, or the calculated remaining time to the next report. An example of the timestamp of the last report is Figure 6 to Figure 7 Similar algorithms can be envisioned for the other 2 options.

[0232] In one embodiment, a new attribute: lastReportTime may be added to type: AmfEventMode (under AmfEventSubscription) as described in 3GPP TS 29.518 v17.5.0 clause 6.2.6.2.6.

[0233] For example, new attributes may be added to Table 6.2.6.2.6-1 of 3GPP TS 29.518 v17.5.0. Table 6.2.6.2.6-1: Definition of AmfEventMode type

[0234] In one embodiment, Annex A.3 of 3GPP TS 29.518 v17.5.0 may be modified as follows.

[0235] Embodiments herein may provide many advantages, and the following is a non-exhaustive list of examples. In some embodiments herein, even if mobility processes between network nodes (e.g., AMF) occur, periodic reports may be processed as expected. Changes in network nodes (e.g., AMF) cannot be perceived by NF service consumers. Embodiments herein are not limited to the above features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description.

[0236] Figure 8a It is shown that it is suitable for practicing some embodiments. For example, any one of the above-mentioned first network node, second network node, source AMF, and target AMF can be implemented as or through device 800.

[0237] The device 800 includes at least one processor 821, such as a digital processor (DP), and at least one memory (MEM) 822 coupled to the processor 821. The device 800 may also include a transmitter TX and a receiver RX 823 coupled to the processor 821. The MEM 822 stores a program (PROG) 824. The PROG 824 may include instructions that, when executed on the associated processor 821, cause the device 800 to operate in accordance with the embodiments of the present disclosure. The combination of at least one processor 821 and at least one MEM 822 may form a processing device 825 suitable for implementing various embodiments of the present disclosure.

[0238] Various embodiments of the present disclosure may be implemented by a computer program executed by one or more processors 821 , software, firmware, hardware, or a combination thereof.

[0239] The MEM 822 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory (as non-limiting examples).

[0240] Processor 821 may be of any type suitable to the local technical environment, and may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture (as non-limiting examples).

[0241] In an embodiment where the apparatus is implemented as or in a first network node, the memory 822 contains instructions executable by the processor 821, whereby the first network node may perform any method performed by the first network node as described above.

[0242] In an embodiment where the apparatus is implemented as or in a second network node, the memory 822 contains instructions executable by the processor 821, so that the second network node can perform any of the methods described above for execution by the second network node.

[0243] In an embodiment where the apparatus is implemented as or at a source AMF, the memory 822 contains instructions executable by the processor 821 so that the source AMF can perform any of the methods performed by the source AMF in the manner described above.

[0244] In an embodiment where the apparatus is implemented as or at a target AMF, the memory 822 contains instructions executable by the processor 821, whereby the target AMF root performs any of the methods described above as performed by the target AMF.

[0245] Figure 8b The block diagram of the first network node 860 according to an embodiment of the present disclosure is shown. As shown in the figure, the first network node 860 includes a determination module 861, which is configured to determine information indicating when the next event report is sent to the network function service consumer. The first network node 860 also includes a sending module 862 for sending the information to the second network node.

[0246] Figure 8c 8 is a block diagram illustrating a second network node 870 according to an embodiment of the present disclosure. As shown, the second network node 870 includes a receiving module 871 configured to receive information from the first network node. The information indicates when the next event report is sent to the network function service consumer. The second network node 870 also includes a sending module 872 for sending the next event report to the network function service consumer based on the information.

[0247] Figure 8d840 is a block diagram illustrating a source AMF 840 according to an embodiment of the present disclosure. As shown in the figure, the source AMF 840 includes a determination module 841 configured to determine that a UE context containing event subscription information should be transmitted to a target AMF during an AMF relocation process. The source AMF 840 may also include a first sending module 842 configured to send event subscription information to the target AMF, indicating when the next event period report is sent to the network function service consumer.

[0248] In one embodiment, the source AMF 840 may further include a receiving module 843 configured to receive an event subscription request for event reporting from a network function service consumer. The event subscription request may include event report information indicating that event reports should be sent periodically.

[0249] In one embodiment, the source AMF 840 may further include a second sending module 844 configured to send event reports to the network function service consumer based on a periodicity.

[0250] Figure 8e 850 is a block diagram showing a target AMF 850 ​​according to an embodiment of the present disclosure. As shown in the figure, the target AMF 850 ​​includes a receiving module 851 for receiving event subscription information from a source AMF, the event subscription information indicating when the next event period report is sent to the network function service consumer. The target AMF 850 ​​also includes a sending module 852 configured to send the next event report to the network function service consumer according to the event subscription information.

[0251] The term "unit" or "module" may have the 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 in this document.

[0252] Through the functional unit, the first network node or the second network node or the source AMF or the target AMF may not require a fixed processor or memory. Any computing resources and storage resources can be arranged from the first network node or the second network node or the source AMF or the target AMF in the communication system. The introduction of virtualization technology and network computing technology can improve the utilization efficiency of network resources and the flexibility of the network.

[0253] An exemplary overall communication system including a terminal device and a network node is further introduced below.

[0254] An embodiment of the present invention provides a communication system, including a host, wherein the host includes: a processing circuit for providing user data; a communication interface for forwarding the user data to a cellular network for transmission to a terminal device, wherein the cellular network includes a base station and / or a terminal device.

[0255] In an embodiment of the present invention, the system further comprises a terminal device. The terminal device is configured to communicate with the base station.

[0256] In an embodiment of the present disclosure, the processing circuit of the host computer is configured to execute a host application to provide user data; and the terminal device includes a processing circuit configured to execute a client application associated with the host application.

[0257] The embodiment of the present disclosure also provides a communication system, including a host, the host including: a communication interface configured to receive user data from a transmission from a terminal device; and a base station. The transmission is from the terminal device to the base station.

[0258] In an embodiment of the present invention, the processing circuit of the host is configured to execute a host application, and the terminal device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host.

[0259] Fig. 9 is a schematic diagram of a wireless network according to some embodiments.

[0260] 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 (e.g. Fig. 9 For simplicity, Fig. 9 The wireless network of FIG. 1 depicts only the network 1006, the network nodes 1060 (corresponding to the network side nodes) and 1060b, and the WDs (corresponding to the terminal devices) 1010, 1010b, and 1010c. In fact, the wireless network may also include any additional elements that are suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a fixed telephone, a service provider, or any other network node or terminal device). In the components shown, the network node 1060 and the wireless device (WD) 1010 are depicted in more detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices to access and / or use the services provided by the wireless network.

[0261] 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 particular standard or other type of predefined rules or procedures. Thus, particular 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.

[0262] The network 1006 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, fiber optic networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0263] The network node 1060 and WD1010 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, 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 can facilitate or participate in the communication of data and / or signals, whether through wired or wireless connections.

[0264] 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 other network nodes or devices in a wireless network to enable 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., wireless access points), base stations (BSs) (e.g., wireless base stations, NodeBs, evolved NodeBs (eNBs), and NRNodeBs (gNBs)). Base stations can be classified according to the coverage they provide (or in other words, their transmit power levels), and may then 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 an antenna-integrated radio. The parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (e.g., MSRBS), network controllers (e.g., radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLC), and / or MDTs. 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, configured, arranged, and / or operable to enable a wireless device to access a wireless network and / or provide a wireless device with access to a wireless network, or to provide some service to a wireless device that has accessed a wireless network.

[0265] exist Fig. 9 In FIG. 1 , the network node 1060 includes a processing circuit 1070, a device readable medium 1080, an interface 1090, an auxiliary device 1084, a power supply 1086, a power supply circuit 1087, and an antenna 1062. Fig. 9The network node 1060 shown in the example wireless network of can represent a device including the combination of hardware components shown, but other embodiments can include network nodes with different combinations of components. It should 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 1060 are depicted as a single box located within a larger box, or nested within multiple boxes, in practice, the network node may include multiple different physical components that make up a single shown component (for example, the device readable medium 1080 may include multiple separate hard drives and multiple RAM modules).

[0266] Similarly, the network node 1060 may be composed of multiple physically independent components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own components. In some cases where the network node 1060 includes multiple independent components (e.g., BTS and BSC components), one or more independent components may be shared between multiple 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 independent network node in some cases. In some embodiments, the network node 1060 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (e.g., independent device-readable media 1080 for different RATs), and some components may be reused (e.g., RATs may share the same antenna 1062). The network node 1060 may also include multiple groups of various components for different wireless technologies integrated into the network node 1060, such as GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1060 .

[0267] The processing circuit 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) provided by the network node as described herein. The operations performed by the processing circuit 1070 may include processing information obtained by the processing circuit 1070, for example, converting the obtained information to 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 based on the processing.

[0268] The processing circuit 1070 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 combination of hardware, software, and / or encoded logic for providing network node 1060 functionality alone or in conjunction with other network node 1060 components (e.g., device readable medium 1080). For example, the processing circuit 1070 may execute instructions stored in the device readable medium 1080 or in a memory within the processing circuit 1070. Such functionality may include providing any of the various wireless features, functions, or advantages discussed herein. In some embodiments, the processing circuit 1070 may include a system on a chip (SOC).

[0269] In some embodiments, processing circuitry 1070 may include one or more radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074. In some embodiments, radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074 may be located on separate chips (or chipsets), circuit boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of RF transceiver circuitry 1072 and baseband processing circuitry 1074 may be located on the same chip or chipset, circuit board, or unit.

[0270] In certain embodiments, some or all of the functionality provided by a network node, base station, eNB, or other such network node described herein may be performed by processing circuit 1070 executing instructions stored on device-readable medium 1080 or memory within processing circuit 1070. In alternative embodiments, some or all of the functionality may be provided by processing circuit 1070 without executing instructions stored on a separate or discrete device-readable medium (e.g., in a hardwired manner). In any of these embodiments, processing circuit 1070 may be configured to perform the functionality described, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuit 1070 itself or other components of network node 1060, but are enjoyed by network node 1060 as a whole and / or end users and wireless networks generally.

[0271] Device readable medium 1080 may include any form of volatile or non-volatile computer readable memory, including but not limited to persistent memory, 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 for storing information, data, and / or instructions that can be used by processing circuit 1070. Device readable medium 1080 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more logic, rules, codes, tables, etc., and / or other instructions that can be executed by processing circuit 1070 and utilized by network node 1060. Device readable medium 1080 may be used to store any computations 1070 performed by processing circuit and / or any data received via interface 1090. In some embodiments, processing circuit 1070 and device readable medium 1080 may be considered integrated.

[0272] Interface 1090 is used for wired or wireless communication of signals and / or data between network node 1060, network 1006 and / or WD1010. As shown, interface 1090 includes port / terminal 1094 for sending and receiving data to network 1006, for example, via a wired connection. Interface 1090 also includes radio front-end circuit 1092, which may be coupled to antenna 1062, or may become part of antenna 1062 in some embodiments. Radio front-end circuit 1092 includes filter 1098 and amplifier 1096. Radio front-end circuit 1092 may be connected to antenna 1062 and processing circuit 1070. Radio front-end circuit may be configured to adjust signals transmitted between antenna 1062 and processing circuit 1070. Radio front-end circuit 1092 may receive digital data to be sent to other network nodes or WDs via a wireless connection. Radio front-end circuit 1092 may convert digital data into radio signals with appropriate channel and bandwidth parameters using a combination of filter 1098 and / or amplifier 1096. The radio signal may then be transmitted via antenna 1062. Similarly, when receiving data, antenna 1062 may collect the radio signal, which may then be converted to digital data by radio front end circuit 1092. The digital data may be passed to processing circuit 1070. In other embodiments, the interface may include different components and / or different combinations of components.

[0273] In some alternative embodiments, the network node 1060 may not include a separate radio front end circuit 1092, and instead, the processing circuit 1070 may include the radio front end circuit and may be connected to the antenna 1062 without the need for a separate radio front end circuit 1092. Similarly, in some embodiments, all or part of the RF transceiver circuit 1072 may be considered part of the interface 1090. In other embodiments, the interface 1090 may include one or more ports or terminals 1094, the radio front end circuit 1092, and the RF transceiver circuit 1072 as part of a radio unit (not shown), and the interface 1090 may communicate with the baseband processing circuit 1074, which is part of the digital unit (not shown).

[0274] Antenna 1062 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1062 may be coupled to radio front end circuit 1090 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1062 may include one or more omnidirectional, sector or panel antennas for sending / receiving radio signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and panel antennas may be line-of-sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, the use of multiple antennas may be referred to as MIMO. In some embodiments, antenna 1062 may be separated from network node 1060 and may be connected to network node 1060 via an interface or port.

[0275] The antenna 1062, the interface 1090 and / or the processing circuit 1070 may be configured to perform any receiving operation and / or certain acquisition operations performed by the network node as described herein. Any information, data and / or signal may be received from the wireless device, another network node and / or any other network device. Similarly, the antenna 1062, the interface 1090 and / or the processing circuit 1070 may be configured to perform any transmitting operation performed by the network node as described herein. Any information, data and / or signal may be transmitted to the wireless device, another network node and / or any other network device.

[0276] The power circuit 1087 may include or be coupled to a power management circuit and is configured to provide power to the components of the network node 1060 to perform the functions described herein. The power circuit 1087 may receive power from the power supply 1086. The power supply 1086 and / or the power circuit 1087 may be configured to provide power to the various components of the network node 1060 in a form suitable for the various components (e.g., at the voltage and current levels required by each of the various components). The power supply 1086 may be included in the power circuit 1087 and / or the network node 1060, or it may be external to the power circuit 1087 and / or the network node 1060. For example, the network node 1060 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a cable), so that the external power source powers the power circuit 1087. As another example, the power supply 1086 may include a power source in the form of a battery or battery pack, which is connected to the power circuit 1087 or integrated in the power circuit 1087. If the external power source fails, the battery can provide backup power. Other types of power sources, such as photovoltaic devices, may also be used.

[0277] Alternative embodiments of network node 1060 may include Fig. 9 , which components may be responsible for providing certain aspects of the network node functionality, including any functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node 1060 may include a user interface device to allow information to be input into the network node 1060 and to allow information to be output from the network node 1060. This may allow a user to perform diagnostics, maintenance, repair, and other management functions for the network node 1060.

[0278] As used herein, a wireless device (WD) refers to a device that is capable, configured, arranged and / or operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD can be used interchangeably with a user equipment (UE). Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for conveying information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human-computer interaction. For example, a WD may be designed to transmit information to a network according to a predetermined schedule, when triggered by an internal or external event, or in response to a request from a network. Examples of WD include, but are not limited to, smartphones, 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, tablet computers, laptops, notebook embedded devices (LEEs), notebook mounted devices (LMEs), smart devices, wireless client devices (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication, such as by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as a D2D communication device. As another specific example, in the Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can 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 (such as refrigerators, TVs, etc.) personal wearable devices (such as watches, fitness trackers, etc.). In other scenarios, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions related to its operation. WD as described above can represent an endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, the WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0279] As shown, wireless device 1010 includes antenna 1011, interface 1014, processing circuit 1020, device readable medium 1030, user interface device 1032, auxiliary device 1034, power supply 1036 and power supply circuit 1037. WD1010 can include multiple groups of one or more of the components shown for different wireless technologies supported by WD1010, such as GSM, WCDMA, LTE, NR, WiFi, WiMAX or Bluetooth wireless technology, to name a few. These wireless technologies can be integrated into the same or different chips or chipsets as other components in WD1010.

[0280] Antenna 1011 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and connected to interface 1014. In some alternative embodiments, antenna 1011 may be separated from WD1010 and may be connected to WD1010 via an interface or port. Antenna 1011, interface 1014 and / or processing circuit 1020 may be configured to perform any receiving or transmitting operation performed by WD described herein. 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 1011 may be considered an interface.

[0281] As shown, the interface 1014 includes a radio front-end circuit 1012 and an antenna 1011. The radio front-end circuit 1012 includes one or more filters 1018 and an amplifier 1016. The radio front-end circuit 1014 is connected to the antenna 1011 and the processing circuit 1020 and is configured to condition the signals transmitted between the antenna 1011 and the processing circuit 1020. The radio front-end circuit 1012 may be coupled to the antenna 1011 or be part of the antenna 1011. In some embodiments, the WD 1010 may not include a separate radio front-end circuit 1012; instead, the processing circuit 1020 may include a radio front-end circuit and may be connected to the antenna 1011. Similarly, in some embodiments, some or all of the RF transceiver circuit 1022 may be considered part of the interface 1014. The radio front-end circuit 1012 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1012 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters 1018 and / or amplifiers 1016. The radio signal may then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1012. The digital data may be passed to processing circuit 1020. In other embodiments, the interface may include different components and / or different combinations of components.

[0282] The processing circuit 1020 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 combination of hardware, software, and / or encoded logic that may provide WD1010 functionality alone or in conjunction with other WD1010 components (e.g., device readable medium 1030). Such functionality may include providing any of the various wireless features or advantages discussed herein. For example, the processing circuit 1020 may execute instructions stored in the device readable medium 1030 or in a memory within the processing circuit 1020 to provide functionality disclosed herein.

[0283] As shown, the processing circuit 1020 includes one or more of the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1020 of the WD1010 may include a SOC. In some embodiments, the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 may be located on a separate chip or chipset. In alternative embodiments, part or all of the baseband processing circuit 1024 and the application processing circuit 1026 may be combined into one chip or chipset, and the RF transceiver circuit 1022 may be located on a separate chip or chipset. In some alternative embodiments, part or all of the RF transceiver circuit 1022 and the baseband processing circuit 1024 may be located on the same chip or chipset, and the application processing circuit 1026 may be located on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuit 1022, baseband processing circuit 1024, and application processing circuit 1026 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuit 1022 may be part of interface 1014. RF transceiver circuit 1022 may condition RF signals for processing circuit 1020.

[0284] In some embodiments, some or all of the functions performed by the WD described herein may be provided by the processing circuit 1020 executing instructions stored on the device-readable medium 1030, which may be a computer-readable storage medium in some embodiments. In alternative embodiments, some or all of the functions may be provided by the processing circuit 1020 without executing instructions stored on a separate or discrete device-readable storage medium (e.g., in a hardwired manner). In any of these specific embodiments, the processing circuit 1020 may be configured to perform the functions described, regardless of whether the instructions stored on the device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 1020 itself or other components of the WD1010, but are generally enjoyed by the WD1010 as a whole and / or end users and wireless networks.

[0285] Processing circuit 1020 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) performed by WD as described herein. Such operations performed by processing circuit 1020 may include processing information obtained by processing circuit 1020, for example, converting the obtained information to other information, comparing the obtained information or the converted information to information stored by WD 1010, and / or performing one or more operations based on the obtained information or the converted information and making determinations based on the processing.

[0286] Device-readable medium 1030 may be used to store computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions executable by processing circuit 1020. Device-readable medium 1030 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., 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 for storing information, data, and / or instructions usable by processing circuit 1020. In some embodiments, processing circuit 1020 and device-readable medium 1030 may be considered integrated.

[0287] The user interface device 1032 may provide a component that allows a human user to interact with the WD1010. This interaction may be in a variety of forms, such as visual, auditory, tactile, etc. The user interface device 1032 may be used to generate output to the user and allow the user to provide input to the WD1010. The type of interaction may vary depending on the type of user interface device 1032 installed in the WD1010. For example, if the WD1010 is a smart phone, the interaction may be performed through a touch screen; if the WD1010 is a smart meter, the interaction may be performed 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 1032 may include input interfaces, devices and circuits and output interfaces, devices and circuits. The user interface device 1032 is configured to allow information to be input into the WD1010 and is connected to the processing circuit 1020 to allow the processing circuit 1020 to process the input information. The user interface device 1032 may include, for example, a microphone, a proximity or other sensor, a key / button, a touch display, one or more cameras, a USB port or other input circuits. The user interface device 1032 is also configured to allow information to be output from the WD 1010, and to allow the processing circuit 1020 to output information from the WD 1010. The user interface device 1032 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 1032, the WD 1010 may communicate with an end user and / or a wireless network, and allow them to benefit from the functionality described herein.

[0288] Auxiliary devices 1034 may be used to provide more specific functions that are not typically performed by WDs. This may include specialized sensors for making measurements for various purposes, interfaces for other communication types (e.g., wired communications), etc. The inclusion and type of components of auxiliary devices 1034 may vary depending on the embodiment and / or scenario.

[0289] In some embodiments, the power supply 1036 may be in the form of a battery or a battery pack. Other types of power supplies may also be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. WD1010 may also include a power supply circuit 1037 for delivering power from the power supply 1036 to various parts of the WD1010 that require power from the power supply 1036 to perform any functions described or indicated herein. In some embodiments, the power supply circuit 1037 may include a power management circuit. The power supply circuit 1037 may additionally or alternatively be used to receive power from an external power source; in this case, the WD1010 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a power cable). In some embodiments, the power supply circuit 1037 may also be operable to deliver power from an external power source to the power supply 1036. This may be used, for example, to charge the power supply 1036. The power supply circuit 1037 may perform any formatting, conversion, or other modifications to the power from the power supply 1036 so that the power is suitable for the various components powered in the WD1010.

[0290] Fig.10 is a schematic diagram of a user equipment according to some embodiments.

[0291] Fig.10 An embodiment of a UE according to various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user, i.e., a human user who owns and / or operates the associated device. Instead, a UE may represent a device that is intended to be sold to or operated by a human user, but may not be associated with a specific human user, or may not initially be associated with a specific 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 a user or operated for the benefit of a user (e.g., a smart meter). UE1100 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 Fig.10 As shown, UE 1100 is an example of a WD configured to communicate according to 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. Therefore, although Fig.10 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0292] exist Fig.10In the embodiment, UE 1100 includes a processing circuit 1101, which is operably coupled to an input / output interface 1105, a radio frequency (RF) interface 1109, a network connection interface 1111, a memory 1115 (including a random access memory (RAM) 1117, a read-only memory (ROM) 1119, and a storage medium 1121, etc.), a communication subsystem 1131, a power supply 1133, and / or any other components, or any combination thereof. The storage medium 1121 includes an operating system 1123, an application 1125, and data 1127. In other embodiments, the storage medium 1121 may include other similar types of information. Some UEs may utilize Fig.10 All components shown in the UE may be used, or only a subset of the components may be utilized. The degree of integration between components may vary from UE to UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0293] exist Fig.10 , processing circuit 1101 may be configured to process computer instructions and data. Processing circuit 1101 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 with appropriate firmware; one or more stored program, general-purpose processors, such as microprocessors or digital signal processors (DSPs), with appropriate software; or any combination of the above. For example, processing circuit 1101 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0294] In the depicted embodiment, the input / output interface 1105 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 1100 may be configured to use an output device via the input / output interface 1105. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to the UE 1100 and output from the UE 1100. 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, other output devices, or any combination thereof. The UE 1100 may be configured to use an input device via the input / output interface 1105 to allow a user to capture information into the UE 1100. 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 key, a touchpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, other similar sensors, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0295] exist Fig.10 In the embodiment of the present invention, the RF interface 1109 can be configured to provide a communication interface with RF components (e.g., a transmitter, a receiver, and an antenna). The network connection interface 1111 can be configured to provide a communication interface with a network 1143a. The network 1143a can 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, other similar networks, or any combination thereof. For example, the network 1143a can include a Wi-Fi network. The network connection interface 1111 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 (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 1111 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit elements, software, or firmware, or can also be implemented separately.

[0296] RAM 1117 may be configured to be connected to processing circuit 1101 via bus 1102 to provide storage or caching of data or computer instructions during execution of software programs (e.g., operating systems, applications, and device drivers). ROM 1119 may be configured to provide computer instructions or data to processing circuit 1101. For example, ROM 1119 may be configured to store unchanged low-level system code or data for basic system functions (e.g., basic input and output (I / O), startup, or receiving keystrokes from a keyboard), which are stored in non-volatile memory. Storage medium 1121 may 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), magnetic disk, optical disk, floppy disk, hard disk, removable cassette, or flash drive. In one example, storage medium 1121 may be configured to include operating system 1123, application 1125 (e.g., a web browser application, a widget or gadget engine, or another application), and data file 1127. The storage medium 1121 may store various operating systems or a combination of operating systems for use by the UE 1100 .

[0297] The storage medium 1121 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy 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 disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) optical drive, an external micro dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a subscriber identity module or a removable user identity (SIM / RUIM) module), other memory, or any combination thereof. The storage medium 1121 may allow the UE 1100 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article of manufacture (e.g., an article of manufacture utilizing a communication system) may be tangibly embodied in the storage medium 1121, which may include a device-readable medium.

[0298] exist Fig.10In the embodiment, the processing circuit 1101 may be configured to communicate with the network 1143b using the communication subsystem 1131. The network 1143a and the network 1143b may be the same network or different networks. The communication subsystem 1131 may be configured to include one or more transceivers for communicating with the network 1143b. For example, the communication subsystem 1131 may be configured to include one or more transceivers for communicating with one or more remote transceivers (e.g., another WD, UE or base station of a radio access network (RAN)) of another device capable of wireless communication according to one or more communication protocols (e.g., IEEE802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver may include a transmitter 1133 and / or a receiver 1135 to respectively implement a transmitter or receiver function suitable for a RAN link (e.g., frequency allocation, etc.). In addition, the transmitter 1133 and the receiver 1135 of each transceiver may share circuit components, software or firmware, or may be implemented separately.

[0299] In the illustrated embodiment, the communication functions of the communication subsystem 1131 may include data communication, voice communication, multimedia communication, short-range communication (e.g., Bluetooth), near-field communication, location-based communication (e.g., using a global positioning system (GPS) to determine location), other similar communication functions, or any combination thereof. For example, the communication subsystem 1131 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1143b 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, other similar networks, or any combination thereof. For example, the network 1143b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1113 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1100.

[0300] The features, advantages and / or functions described herein may be implemented in one of the components of UE1100, or divided into multiple components of UE1100. In addition, the features, advantages and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1131 may be configured to include any component described herein. In addition, the processing circuit 1101 may be configured to communicate with any such component via the bus 1102. In another example, any such component may be represented by program instructions stored in a memory, and when the processing circuit 1101 executes these program instructions, the corresponding functions described herein are performed. In another example, the functions of any such component may be divided between the processing circuit 1101 and the communication subsystem 1131. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0301] Fig.11 is a schematic diagram of a virtualization environment according to some embodiments.

[0302] Fig.11 12 is a schematic block diagram illustrating a virtualized environment 1200 in which the functionality implemented in certain embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized wireless 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 functionality being implemented as one or more virtual components (e.g., by one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0303] 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 1200 hosted by one or more hardware nodes 1230. Furthermore, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0304] These functions may be implemented by one or more applications 1220 (also referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), which are operable to implement some features, functions, and / or advantages of some embodiments disclosed herein. The applications 1220 run in a virtualized environment 1200, which provides hardware 1230, which includes processing circuits 1260 and memory 1290-1. The memory 1290-1 contains instructions 1295 that can be executed by the processing circuits 1260, whereby the applications 1220 are operable to provide one or more features, advantages, and / or functions disclosed herein.

[0305] The virtualized environment 1200 includes a general or special purpose network hardware device 1230, which includes a set of one or more processors or processing circuits 1260, which may be commercial off-the-shelf (COTS) processors, 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 1290-1, which may be a non-persistent memory for temporarily storing instructions 1295 or software executed by the processing circuit 1260. Each hardware device may include one or more network interface controllers (NICs) 1270, also known as network interface cards, which include physical network interfaces 1280. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 1290-2, in which software 1295 and / or instructions executed by the processing circuit 1260 are stored. The software 1295 may include any type of software, including software for instantiating one or more virtualization layers 1250 (also known as hypervisors), software for executing virtual machines 1240, and software that enables them to perform the functions, features, and / or advantages associated with some embodiments described herein.

[0306] The virtual machine 1240 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of instances of the virtual device 1220 can be implemented on one or more virtual machines 1240 and can be implemented in different ways.

[0307] During operation, processing circuitry 1260 executes software 1295 to instantiate a hypervisor or virtualization layer 1250, sometimes referred to as a virtual machine monitor (VMM). Virtualization layer 1250 can present a virtual operating platform to virtual machines 1240 that appears to be network hardware.

[0308] like Fig.11As shown, hardware 1230 can be an independent network node with common or specific components. Hardware 1230 can include antenna 12225, and certain functions can be implemented through virtualization. Alternatively, hardware 1230 can be part of a larger hardware cluster (for example, in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed by management and orchestration (MANO) 12100, where management and orchestration are responsible for overseeing the life cycle management of application 1220.

[0309] In some cases, hardware virtualization is referred to as network function virtualization (NFV). NFV can be used to consolidate multiple types of network equipment onto industry-standard high-capacity server hardware, physical switches, and physical storage, which can be located in data centers and on client devices.

[0310] In the context of NFV, a virtual machine 1240 may be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine 1240 and the portion of the hardware 1230 on which it executes (whether dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 1240) form a separate virtual network element (VNE).

[0311] 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 1240 on top of the hardware network infrastructure 1230 and corresponds to Fig.11 Application 1220 in.

[0312] In some embodiments, one or more radio units 12200, each including one or more transmitters 12220 and one or more receivers 12210, may be coupled to one or more antennas 12225. The radio unit 12200 may communicate directly with the hardware node 1230 via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide a virtual node with radio functionality, such as a radio access node or base station.

[0313] In some embodiments, some signaling may be implemented using a control system 12230 , which may alternatively be used for communications between the hardware node 1230 and the radio unit 12200 .

[0314] Fig.12 is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediate network, according to some embodiments.

[0315] refer to Fig.12According to one embodiment, the communication system includes a telecommunication network 1310, such as a cellular network of the 3GPP type, which includes an access network 1311, such as a wireless access network, and a core network 1314. The access network 1311 includes a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c may be connected to the core network 1314 via a wired or wireless connection 1315. A UE 1391 located in the coverage area 1313c is configured to be wirelessly connected to or paged by the corresponding base station 1312c. A relay UE 1392 in the coverage area 1313a may be wirelessly connected to the corresponding base station 1312a. Although multiple UEs 1391, 1392 are shown in this example, the disclosed embodiments are also applicable to the case where a single UE is in the coverage area or a single UE is connected to the corresponding base station 1312a or 1312b or 1312c.

[0316] The telecommunications network 1310 itself is connected to a host 1330, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-enabled server, a distributed server, or as a processing resource in a server farm. The host 1330 may be owned or controlled by a service provider, or may be operated by or on behalf of a service provider. The connections 1321 and 1322 between the telecommunications network 1310 and the host 1330 may extend directly from the core network 1314 to the host 1330, or may be made through an optional intermediate network 1320. The intermediate network 1320 may be one of a public, private, or managed network, or a combination of multiple; the intermediate network 1320 (if any) may be a backbone network or the Internet; specifically, the intermediate network 1320 may include two or more sub-networks (not shown).

[0317] Fig.12The communication system as a whole realizes the connection between the connected UE1391, 1392 and the host 1330. The connection can be described as an over-the-top (OTT) connection 1350. The host 1330 and the connected UE1391, 1392 are configured to transmit data and / or signaling through the OTT connection 1350, using the access network 1311, the core network 1314, any intermediate network 1320 and possible other infrastructure (not shown) as intermediaries. The OTT connection 1350 can be transparent because the participating communication devices through which the OTT connection 1350 passes do not know the routing of uplink and downlink communications. For example, the base station 1312a or 1312b or 1312c may not or need to be informed of the past routing of the incoming downlink communication of the data from the host computer 1330 in order to forward (e.g., handover) to the connected UE1391. Similarly, base stations 1312a or 1312b or 1312c need not be aware of future routing of outgoing uplink communications from UE 1391 toward host computer 1330 .

[0318] Fig.13 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.

[0319] Now refer to Fig.13 Describe an example implementation of a UE, a base station, and a host according to an embodiment. In the communication system 1400, the host 1410 includes hardware 1415, including a communication interface 1416, which is configured to establish and maintain a wired or wireless connection with an interface of different communication devices of the communication system 1400. The host 1410 also includes a processing circuit 1418, which may have storage and / or processing capabilities. Specifically, the processing circuit 1418 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 1410 also includes software 1411, which is stored in the host computer 1410 or accessible by the host computer 1410, and can be executed by the processing circuit 1418. Software 1411 includes a host application 1412. The host application 1412 can be used to provide services to remote users, such as UE1430 connected by an OTT connection 1450 terminating at the UE1430 and the host computer 1410. When providing services to remote users, the host application 1412 may provide user data transmitted using the OTT connection 1450 .

[0320] The communication system 1400 also includes a base station 1420, which is set in the telecommunication system and includes hardware 1425 to enable it to communicate with the host 1410 and the UE 1430. The hardware 1425 may include a communication interface 1426 for establishing and maintaining a wired or wireless connection with the interface of different communication devices of the communication system 1400, and a radio interface 1427 for establishing and maintaining a connection with a network located in the coverage area ( Fig.13 The communication interface 1426 may be configured to facilitate connection 1460 to the host 1410. The connection 1460 may be direct or may be through a core network (eg, a wireless network) of the telecommunications system. Fig.13 1420) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1425 of the base station 1420 also includes processing circuitry 1428, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown), adapted to execute instructions. The base station 1420 also has software 1421 stored internally or accessible via an external connection.

[0321] The communication system 1400 also includes the aforementioned UE 1430. Its hardware 1435 may include a radio interface 1437, which is configured to establish and maintain a wireless connection 1470 with a base station serving the coverage area where the UE 1430 is currently located. The hardware 1435 of the UE 1430 also includes a processing circuit 1438, 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 1430 also includes software 1431, which is stored in the UE 1430 or can be accessed by the UE 1430 and can be executed by the processing circuit 1438. The software 1431 includes a client application 1432. The client application 1432 can be used to provide services to human or non-human users through the UE 1430 with the support of the host 1410. In the host 1410, the executing host application 1412 can communicate with the executing client application 1432 through the OTT connection 1450 terminated at the UE 1430 and the host 1410. When providing services to users, the client application 1432 can receive request data from the host application 1412 and provide user data in response to the request data. The OTT connection 1450 can transmit the request data and the user data. The client application 1432 can interact with the user to generate the user data it provides.

[0322] It is worth noting that Fig.13 The host 1410, base station 1420 and UE 1430 shown in FIG. Fig.12The host 1330, one of the base stations 1312a, 1312b, 1312c, and one of the UEs 1391, 1392 in the embodiment are similar or identical. That is, the internal workings of these entities may be as follows: Fig.13 shown, and independently, the surrounding network topology can be Fig.12 The network topology shown.

[0323] exist Fig.13 , an OTT connection 1450 is abstractly drawn to illustrate communications between a host 1410 and a UE 1430 through a base station 1420, without explicit reference to any intermediate devices and the precise routing of messages through those devices. The network infrastructure can determine the routing, which can be configured to hide the routing from the UE 1430 or the service provider operating the host 1410, or from both. While the OTT connection 1450 is active, the network infrastructure can further make decisions by which the routing is dynamically changed (e.g., based on load balancing considerations or network reconfiguration).

[0324] The wireless connection 1470 between UE 1430 and base station 1420 is consistent with the teachings of the embodiments described in the present disclosure. One or more of the various embodiments improves the performance of OTT services provided to UE 1430 using OTT connection 1450, where the wireless connection 1470 constitutes the last segment. More specifically, in some embodiments herein, periodic reports can be processed as expected even if inter-network node (e.g., AMF) mobility procedures occur. Changes in network nodes (e.g., AMF) cannot be perceived by NF service consumers.

[0325] A measurement program may be provided for monitoring data rates, delays, and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 1450 between the host computer 1410 and the UE 1430 in response to changes in the measurement results. The measurement program and / or the network function for reconfiguring the OTT connection 1450 may be implemented in the software 1411 and hardware 1415 of the host computer 1410, or in the software 1431 and hardware 1435 of the UE 1430, 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 1450 passes; the sensor may participate in the measurement program by providing the values ​​of the above-mentioned monitored quantities or providing the values ​​of other physical quantities, from which the software 1411, 1431 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1450 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 1420, and it may be unknown or imperceptible to the base station 1420. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling to facilitate host 1410 measurements of throughput, propagation time, latency, etc. The measurements may be implemented by software 1411 and 1431 that transmit messages, particularly null messages or "dummy" messages, using OTT connection 1450 while monitoring propagation time, errors, etc.

[0326] Fig.14 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0327] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.12 and 13 To simplify the present disclosure, this section will only include Fig.14 Drawing reference. In step 1510, the host provides user data. In sub-step 1511 of step 1510 (which may be optional), the host provides the user data by executing a host application. In step 1520, the host initiates a transmission carrying the user data to the UE. In step 1530 (which may be optional), the base station transmits the user data carried in the host-initiated transmission to the UE in accordance with the teachings of the embodiments described in the present disclosure. In step 1540 (which may also be optional), the UE executes a client application associated with the host application executed by the host.

[0328] Fig.15is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0329] Fig.15 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.12 and 13 To simplify the present disclosure, this section will only include Fig.15 Drawing reference of. In step 1610 of the method, the host provides user data. In an optional sub-step (not shown), the host provides the user data by executing a host application. In step 1620, the host initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described in the present disclosure, the transmission can be delivered by a base station. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

[0330] Fig.16 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments.

[0331] Fig.16 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.12 and 13 To simplify the present disclosure, this section will only include Fig.16 Drawing reference. In step 1710 (which may be optional), the UE receives input data provided by the host. Additionally or alternatively, in step 1720, the UE provides user data. In sub-step 1721 of step 1720 (which may be optional), the UE provides user data by executing a client application. In sub-step 1711 of step 1710 (which may be optional), the UE executes a client application that provides user data in response to received input data provided by the host. 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, the UE initiates the transfer of the user data to the host computer in sub-step 1730 (optional). In step 1740 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described in the present disclosure.

[0332] Fig.17 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0333] Fig.17 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.12 and 13 To simplify the present disclosure, this section will only include Fig.17 Drawing reference. In step 1810 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described in the present disclosure. In step 1820 (which may be optional), the base station initiates transmission of the received user data to the host. In step 1830 (which may be optional), the host receives the user data carried in the transmission initiated by the base station.

[0334] According to one aspect of the present disclosure, there is provided a computer program product, which is tangibly stored on a computer-readable storage medium and includes instructions, which when executed on at least one processor, cause the at least one processor to perform any of the methods described above.

[0335] According to one aspect of the present disclosure, a computer-readable storage medium is provided, storing instructions, which, when executed by at least one processor, enable the at least one processor to perform any of the methods described above.

[0336] In addition, the present invention may also provide a carrier containing the above-mentioned computer program, wherein the carrier is one of an electronic signal, an optical signal, a wireless signal or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device, such as a RAM (random access memory), a ROM (read-only memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.

[0337] The techniques described herein can be implemented by various means, so that the device for implementing one or more functions of the corresponding device described in the embodiment includes not only the prior art means, but also means for implementing one or more functions of the corresponding device described in the embodiment, and it may include a separate means for each separate function, or it may be configured as a means for performing two or more functions. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For firmware or software, it can be implemented by a module (e.g., a program, a function, etc.) that performs the functions described herein.

[0338] The block diagrams and flow charts of the apparatus and devices describe exemplary embodiments of the present invention. It should be understood that each block in the block diagrams and flow charts and the combination of blocks in the block diagrams and flow charts, respectively, can be implemented by various means including computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed on the computer or other programmable data processing device create means for implementing the functions specified in the flow chart blocks.

[0339] In addition, although the operations are shown in a particular order, it should not be understood that these operations are required to be performed in the particular order or sequence shown, or that all the operations shown are required to be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, they should not be interpreted as limitations on the scope of the subject matter described herein, but should be interpreted as descriptions of the features of specific embodiments. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0340] Although this specification contains many specific implementation details, these details should not be interpreted as limitations on any implementation or the scope of what may be claimed, but rather as descriptions of features of specific embodiments of specific implementations. Certain features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments. In addition, although features may be described as working in certain combinations or even initially claimed, in some cases one or more features in the claimed combination may be deleted from the combination, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination.

[0341] It is obvious to those skilled in the art that, with the advancement of technology, the concept of the present invention can be implemented in various ways. The above embodiments are only used to describe the present invention, not to limit the present invention, and those skilled in the art will appreciate that various modifications and changes can be made without departing from the spirit and scope of the present invention. These modifications and changes are considered to belong to the scope of the present invention and the appended claims. The scope of protection of the present invention is defined by the appended claims.

Claims

1. A method (310) performed by a source access and mobility management function (AMF), comprising: determining (312) that during the AMF relocation procedure, the UE context including the event subscription information should be transferred to the target AMF; as well as The event subscription information is sent (314) to the target AMF, wherein the event subscription information indicates when the next event period report is sent to the network function service consumer.

2. The method according to claim 1, wherein: The event subscription information includes at least one of the following: The timestamp of when the last event report was generated and notified to the network function service consumer, or The timestamp of the next event report, or Calculate the remaining time for the next event report.

3. The method according to claim 1 or 2, wherein the event subscription exists in an event subscription when the event subscription is transferred from the source AMF to the target AMF and an event trigger is set to periodic.

4. The method according to claim 3, wherein: The event subscription includes at least one of the following: The cycle time for incident reporting, the maximum number of reports that can be generated by the subscription events in the event subscription, or The time after which subscribed events will stop generating reports and the subscription will become invalid.

5. The method according to any one of claims 1 to 4, wherein: The determining that the UE context including the event subscription information should be transferred to the target AMF comprises: A message is received from a source Next Generation Radio Access Network (NG-RAN) node indicating that a handover is required.

6. The method according to any one of claims 1 to 5, further comprising: receiving (322) an event subscription request for an event report from a network function service consumer, wherein the event subscription request includes event report information indicating that the event report should be sent periodically; and The event report is sent (324) to the network function service consumer on a periodic basis.

7. The method according to any one of claims 1 to 6, wherein: The network function service consumer includes at least one of the following: Network Open Function (NEF), Session Management Function (SMF), Unified Data Management (UDM), Network Data Analysis Function (NWDAF), Application Function (AF), Location Management Function (LMF), or Gateway Mobile Location Centre (GMLC).

8. The method according to any one of claims 1-7, wherein the event subscription information is sent to the target AMF in a mobility registration update with an AMF relocation procedure or a handover with an AMF relocation procedure.

9. A method (410) performed by a target access and mobility management function (AMF), comprising: receiving (412) event subscription information from a source AMF, wherein the event subscription information indicates when a next event period report is to be sent to a network function service consumer; and The next event report is sent (414) to the network function service consumer according to the event subscription information.

10. The method according to claim 9, wherein the event subscription information includes at least one of the following: The timestamp of when the last event report was generated and notified to the network function service consumer, or The timestamp of the next event report, or The calculated time remaining until the next incident report.

11. The method according to claim 9 or 10, wherein the event subscription information exists when the event subscription is transferred from the source AMF to the target AMF and an event trigger is set to periodicity.

12. The method according to claim 11, wherein: Event subscriptions include at least one of the following: The cycle time for incident reporting, or the maximum number of reports that can be generated by the subscription events in the event subscription, or The time after which subscribed events will stop generating reports and the subscription will expire.

13. The method according to any one of claims 9 to 12, wherein: The network function service consumer includes at least one of the following: Network Open Function (NEF), Session Management Function (SMF), Unified Data Management (UDM), Network Data Analysis Function (NWDAF), Application Function (AF), Location Management Function (LMF), or Gateway Mobile Location Centre (GMLC).

14. The method according to any one of claims 9-13, wherein the event subscription information is received from the source AMF in a mobility registration update with an AMF relocation procedure or a handover with an AMF relocation procedure.

15. The method according to any one of claims 9 to 14, wherein: Sending the next event report to the network function service consumer according to the event subscription information includes: Based on the event subscription information, determining (514) a remaining time of a start timer of the source AMF; When the remaining time is greater than zero, starting (516) a timer based on the remaining time, and sending the next event report to the network function service consumer when the timer expires; and When the remaining time is equal to or less than zero, the next event report is sent (518) to the network function service consumer.

16. A source access and mobility management function AMF (800), comprising: Processor(821); as well as A memory (822) coupled to the processor (821), the memory (822) containing instructions executable by the processor (821), whereby the source AMF (800) is operable to: Determine that the UE context including event subscription information shall be transferred to the target AMF during the AMF relocation procedure; as well as The event subscription information is sent to the target AMF, where the event subscription information indicates when the next event cycle report is sent to the network function service consumer.

17. The source AMF according to claim 16, wherein the source AMF is further operable to perform the method according to any one of claims 2 to 8.

18. A target access and mobility management function AMF (800), comprising: Processor(821); as well as A memory (822) coupled to the processor (821), the memory (822) containing instructions executable by the processor (821), whereby the target AMF (800) is operable to: Receiving event subscription information from a source AMF, wherein the event subscription information indicates when a next event cycle report is to be sent to a network function service consumer; and Send the next event report to the network function service consumer according to the event subscription information.

19. The target AMF according to claim 18, wherein: The target AMF is further operable to perform the method as claimed in any one of claims 10 to 15.

20. A computer-readable storage medium storing instructions, which, when executed by at least one processor, causes the at least one processor to perform the method according to any one of claims 1 to 15.

21. A computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 15.

Images