WO2023179483A9 - Procédé et appareil pour la mise en sourdine de notification d'état d'application - Google Patents

Procédé et appareil pour la mise en sourdine de notification d'état d'application Download PDF

Info

Publication number
WO2023179483A9
WO2023179483A9 PCT/CN2023/082167 CN2023082167W WO2023179483A9 WO 2023179483 A9 WO2023179483 A9 WO 2023179483A9 CN 2023082167 W CN2023082167 W CN 2023082167W WO 2023179483 A9 WO2023179483 A9 WO 2023179483A9
Authority
WO
WIPO (PCT)
Prior art keywords
notification
condition
message
network entity
application status
Prior art date
Application number
PCT/CN2023/082167
Other languages
English (en)
Other versions
WO2023179483A1 (fr
Inventor
Hui Yang
Feng Yu
Susana Fernandez Alonso
Fuencisla Garcia Azorero
Jinyin Zhu
Erik WIKSTRÖEM
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023179483A1 publication Critical patent/WO2023179483A1/fr
Publication of WO2023179483A9 publication Critical patent/WO2023179483A9/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements

Definitions

  • the present disclosure relates generally to the technology of communication, and in particular, to a method and an apparatus for muting a notification of application status.
  • ADC application detection and control
  • the PCEF/SMF shall report, if the PCRF/PCF has subscribed to the event, unless the notification is muted for the specific PCC Rule, to the PCRF/PCF.
  • a first aspect of the present disclosure provides a method performed by a first network entity.
  • the method comprises: muting a notification of application status, when a condition is met, and/or activating the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the application status may be about an application on a terminal device.
  • the application status may include a start or a stop of a traffic of the application.
  • the method may further comprise: receiving from a second network entity a first message indicating the condition.
  • the first message may be a message for provisioning a policy and charging control, PCC, Rule.
  • the first message may comprise at least one of:a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the PCC rule may include the condition.
  • the first message may include at least one of:condition data for indicating the condition, or an indication about whether to mute the notification of application status or to activate the notification of application status.
  • the notification of application status may be transmitted from the first network entity to the second network entity, when the notification of application status is activated.
  • the first network entity may comprise a session management function, SMF, or a packet data network gateway control plane, PGW-C.
  • the second network entity may comprise a policy control function, PCF, or a policy and charging rules function, PCRF.
  • the application status may be obtained via a third network entity.
  • the third network entity may comprise a user plane function, UPF, or a packet data network gateway user plane, PGW-U.
  • the method may further comprise: receiving from a second network entity a second message for muting the notification of application status.
  • the second message may be transmitted by the second network entity, when the second network entity determines that the condition is met.
  • the second message may be a message for modifying a session management policy.
  • the second message may comprise at least one of: a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the second message may include at least one of: an indication to mute the notification of application status, or condition data for indicating the condition.
  • the method may further comprise: receiving from the second network entity a third message for activating the notification of application status.
  • the third message may be transmitted by the second network entity, when the second network entity determines that the condition is not met.
  • the third message may be a message for modifying a session management policy.
  • the third message may comprise at least one of: a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the third message may include at least one of: an indication to activate the notification of application status, or condition data for indicating the condition.
  • the condition may comprise a time period.
  • the time period comprises a mute notification activation time and/or a mute notification deactivation time.
  • the condition may comprise an area.
  • the area may be where a terminal device is located.
  • the notification of application status is muted, based on whether the terminal device presence status is in the area or out of the area.
  • the condition may comprise an occurrence of an event, and/or a subscription.
  • a second aspect of the present disclosure provides a method performed by a second network entity.
  • the method comprises: muting a notification of application status, when a condition is met, and/or activating the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the application status may be about an application on a terminal device.
  • the application status may include a start or a stop of a traffic of the application.
  • the method may further comprise: transmitting to a first network entity a first message indicating the condition.
  • the first message may be a message for provisioning a policy and charging control, PCC, Rule.
  • the first message may comprise at least one of:a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the PCC rule may include the condition.
  • the first message may include at least one of:condition data for indicating the condition, or an indication about whether to mute the notification of application status or to activate the notification of application status.
  • the notification of application status may be transmitted from the first network entity to the second network entity, when the notification of application status is activated.
  • the first network entity may comprise a session management function, SMF, or a packet data network gateway control plane, PGW-C.
  • the second network entity may comprise a policy control function, PCF, or a policy and charging rules function, PCRF.
  • the application status may be obtained via a third network entity.
  • the third network entity may comprise a user plane function, UPF, or a packet data network gateway user plane, PGW-U.
  • the method may further comprise: transmitting to a first network entity a second message for muting the notification of application status.
  • the second message may be transmitted by the second network entity, when the second network entity determines that the condition is met.
  • the second message may be a message for modifying a session management policy.
  • the second message may comprise at least one of: a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the second message may include at least one of: an indication to mute the notification of application status, or condition data for indicating the condition.
  • the method may further comprise: transmitting to a first network entity a third message for activating the notification of application status.
  • the third message may be transmitted by the second network entity, when the second network entity determines that the condition is not met.
  • the third message may be a message for modifying a session management policy.
  • the third message may comprise at least one of: a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the third message may include at least one of: an indication to activate the notification of application status, or condition data for indicating the condition.
  • the condition may comprise a time period.
  • the time period comprises a mute notification activation time and/or a mute notification deactivation time.
  • the condition may comprise an area.
  • the area may be where a terminal device is located.
  • the notification of application status is muted, based on whether the terminal device presence status is in the area or out of the area.
  • the condition may comprise an occurrence of an event, and/or a subscription.
  • a third aspect of the present disclosure provides an apparatus for a first network entity in a communication network.
  • the apparatus comprises: a processor, and a memory.
  • the memory may contain instructions executable by the processor.
  • the apparatus for the first network entity may be operative for: muting a notification of application status, when a condition is met, and/or activating the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the apparatus may be further operative to perform the method according to any embodiment above mentioned.
  • a fourth aspect of the present disclosure provides an apparatus for a second network entity in a communication network.
  • the apparatus comprises: a processor, and a memory.
  • the memory contains instructions executable by the processor.
  • the apparatus for the second network entity is operative for: muting a notification of application status, when a condition is met, and/or activating the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the apparatus may be further operative to perform the method according to any embodiment above mentioned.
  • a fifth aspect of the present disclosure provides a computer-readable storage medium storing instructions. When the instructions are executed by at least one processor, cause the at least one processor to perform the method according to any embodiment above mentioned.
  • Embodiments herein afford many advantages. According to embodiments of the present disclosure, an improved manner for muting a notification of application status may be provided.
  • the notification may be muted dynamically, based on a specific condition. Therefore, the configuration about muting the notification may be modified, even during PCC rule life cycle.
  • FIG. 1A is a flow chart illustrating a method performed by a first network entity, in accordance with some embodiments of the present disclosure.
  • FIG. 1B is a flow chart illustrating additional steps of the method shown in FIG. 1A.
  • FIG. 2A is a flow chart illustrating a method performed by a first network entity, in accordance with some embodiments of the present disclosure.
  • FIG. 2B is a flow chart illustrating additional steps of the method shown in FIG. 2A.
  • FIG. 3 is a diagram showing exemplary messages and procedures for the proposed method, in accordance with some embodiments of the present disclosure.
  • FIG. 4A is a diagram showing detailed steps for a first exemplary procedure.
  • FIG. 4B is a diagram showing detailed steps for a second exemplary procedure.
  • FIG. 4C is a diagram showing detailed steps for a third exemplary procedure.
  • FIG. 5A is a diagram showing detailed steps for a fourth exemplary procedure.
  • FIG. 5B is a diagram showing detailed steps for a fifth exemplary procedure.
  • FIG. 5C is a diagram showing detailed steps for a sixth exemplary procedure.
  • FIG. 6 is a block diagram showing an exemplary apparatus for a first network entity, which is suitable for perform the method according to embodiments of the disclosure.
  • FIG. 7 is a block diagram showing an exemplary apparatus for a second network entity, which is suitable for perform the method according to embodiments of the disclosure.
  • FIG. 8 is a block diagram showing an apparatus/computer readable storage medium, according to embodiments of the present disclosure.
  • FIG. 9A is a block diagram showing units of an exemplary apparatus for a first network entity, which is suitable for perform the method according to embodiments of the disclosure.
  • FIG. 9B is a block diagram showing units of an exemplary apparatus for a second network entity, which is suitable for perform the method according to embodiments of the disclosure.
  • FIG. 10 shows an example of a communication system 1000 in accordance with some embodiments.
  • FIG. 11 shows a UE 1100 in accordance with some embodiments.
  • FIG. 12 shows a network node 1200 in accordance with some embodiments.
  • FIG. 13 is a block diagram of a host 1300, which may be an embodiment of the host 1016 of FIG. 10, in accordance with various aspects described herein.
  • FIG. 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized.
  • FIG. 15 shows a communication diagram of a host 1502 communicating via a network node 1504 with a UE 1506 over a partially wireless connection in accordance with some embodiments.
  • the term “network” or “communication network” refers to a network following any suitable communication standards (such for an internet network, or any wireless network) .
  • wireless communication standards may comprise new radio (NR) , long term evolution (LTE) , LTE-Advanced, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , Code Division Multiple Access (CDMA) , Time Division Multiple Address (TDMA) , Frequency Division Multiple Access (FDMA) , Orthogonal Frequency-Division Multiple Access (OFDMA) , Single carrier frequency division multiple access (SC-FDMA) and other wireless networks.
  • NR new radio
  • LTE long term evolution
  • WCDMA high-speed packet access
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Address
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single carrier frequency division multiple access
  • the communications between two devices in the network may be performed according to any
  • network entity refers to a network device or network node or network function or any other devices (physical or virtual) in a communication network.
  • the network entity in the network may include a base station (BS) , an access point (AP) , a multi-cell/multicast coordination entity (MCE) , a server node/function (such as a service capability server/application server, SCS/AS, group communication service application server, GCS AS, application function, AF) , an exposure node/function (such as a service capability exposure function, SCEF, network exposure function, NEF) , a unified data management, UDM, a home subscriber server, HSS, a session management function, SMF, an access and mobility management function, AMF, a mobility management entity, MME, a controller or any other suitable device in a wireless communication network.
  • BS base station
  • AP access point
  • MCE multi-cell/multicast coordination entity
  • server node/function such as a service capability server/application server, SCS/AS,
  • the BS may be, for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNodeB or gNB) , a remote radio unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth.
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • gNodeB or gNB next generation NodeB
  • RRU remote radio unit
  • RH radio header
  • RRH remote radio head
  • relay a low power node such as a femto, a pico, and so forth.
  • the network entity may comprise multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, positioning nodes and/or the like.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • positioning nodes positioning nodes and/or the like.
  • the term “network node” , “network function” , “network entity” herein may also refer to any suitable node, function, entity which can be implemented (physically or virtually) in a communication network.
  • the 5G system may comprise a plurality of NFs such as AMF (Access and mobility Function) , SMF (Session Management Function) , AUSF (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 proxy) , etc.
  • the network function may comprise different types of NFs (such as PCRF (Policy and Charging Rules Function) , etc. ) for example depending on the specific network.
  • terminal device refers to any end device that can access a communication network and receive services therefrom.
  • the terminal device refers to a mobile terminal, user equipment (UE) , or other suitable devices.
  • the UE may be, for example, a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, 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 laptop-embedded equipment (LEE) , a laptop-mounted equipment (LME) , a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like.
  • a portable computer an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance
  • a mobile phone a cellular phone, a smart phone, a voice over IP (VoIP) phone
  • a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP, such as 3GPP’ LTE standard or NR standard.
  • 3GPP 3GPP’ LTE standard or NR standard.
  • a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device.
  • a terminal device may be configured to transmit and/or receive information without direct human interaction.
  • 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 requests from the communication network.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
  • a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment.
  • the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • references in the specification to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and 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. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the phrase “at least one of A and (or) B” should be understood to mean “only A, only B, or both A and B. ”
  • the phrase “A and/or B” should be understood to mean “only A, only B, or both A and B. ”
  • muting notification needs to be activated or deactivated based on dynamic condition like Presence Reporting Area (PRA) or Time of Date (ToD) , etc.
  • PRA Presence Reporting Area
  • ToD Time of Date
  • PCF needs to be informed of application start/stop status in order to enforce high bandwidth and low latency slice to the UE if an application is started.
  • the PCF doesn’ t care about application start/stop status, since average bandwidth is always applied.
  • reporting of application status is unnecessary and increases the signalling between the PCF and the SMF.
  • Another example could be that, in the busy hours, a specific QoS policy would be applied dependent on the application status (APP_START/APP_STOP) , in order to best utilize the network resource. But beyond the busy hours, the general QoS profile could be applied regardless of application status, in order to provide a better user experience for the subscriber, and the PCF needn’ t to receive the report of the application status anymore.
  • muting notification needs to be activated/deactivated during the lifecycle of a PCC rule.
  • FIG. 1A is a flow chart illustrating a method performed by a first network entity, in accordance with some embodiments of the present disclosure.
  • the method 100 is performed by a first network entity.
  • the method 100 comprises: a step S102, muting a notification of application status, when a condition is met; and/or a step S104, activating the notification of application status, when the condition is not met.
  • the notification of application status may be muted or not muted (activated) based on a condition. Therefore, a dynamic configuration for the notification of application status may be achieved.
  • the condition may be a mute notification condition.
  • the application status may be about an application on a terminal device.
  • the application status may include a start or a stop of a traffic of the application.
  • FIG. 1B is a flow chart illustrating additional steps of the method shown in FIG. 1A.
  • the method 100 may further comprise: a step S 106, receiving from a second network entity a first message indicating the condition.
  • the first message may be a message for provisioning a policy and charging control, PCC, Rule.
  • the first message may comprise at least one of:a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the PCC rule may include the condition.
  • the first message may include at least one of:condition data for indicating the condition, or an indication about whether to mute the notification of application status or to activate the notification of application status.
  • the response for policy control create may be “Npcf_SMPolicyControl_Create Response” .
  • the response for policy control update may be “Npcf_SMPolicyControl_Update Response” .
  • the notification for policy control update may be “Npcf_SMPolicyControl_UpdateNotify” .
  • the condition data may be “muteNotifCondData” below described in embodiments.
  • the indication may be “muteNotif” below described in embodiments.
  • the notification of application status may be transmitted from the first network entity to the second network entity, when the notification of application status is activated.
  • the first network entity may determine whether the condition is met by itself, and actively mute or activate the notification of the application status.
  • the signalling between the first network entity, and the second network entity may be reduced.
  • the first network entity may comprise a session management function, SMF, or a packet data network gateway control plane, PGW-C.
  • the second network entity may comprise a policy control function, PCF, or a policy and charging rules function, PCRF.
  • the application status may be obtained via a third network entity.
  • the third network entity may comprise a user plane function, UPF, or a packet data network gateway user plane, PGW-U.
  • the method 100 may further comprise: a step S108, receiving from a second network entity a second message for muting the notification of application status.
  • the second message may be transmitted by the second network entity, when the second network entity determines that the condition is met.
  • the second message may be a message for modifying a session management policy.
  • the second message may comprise at least one of: a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the second message may include at least one of: an indication to mute the notification of application status, or condition data for indicating the condition.
  • the method 100 may further comprise: a step S110, receiving from the second network entity a third message for activating the notification of application status.
  • the third message may be transmitted by the second network entity, when the second network entity determines that the condition is not met.
  • the third message may be a message for modifying a session management policy.
  • the third message may comprise at least one of: a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the third message may include at least one of: an indication to activate the notification of application status, or condition data for indicating the condition.
  • the first network entity may mute or activate the notification of the application status.
  • the first network entity needs not to determine whether the condition is met or not by itself. A compatibility may be ensured.
  • the condition may comprise a time period.
  • the time period comprises a mute notification activation time and/or a mute notification deactivation time.
  • the condition may comprise an area.
  • the area may be where a terminal device is located.
  • the notification of application status is muted, based on whether the terminal device presence status is in the area or out of the area.
  • the condition may comprise an occurrence of an event, and/or a subscription.
  • the method 100 may comprises any one or more of the additional steps S106, S108, S110.
  • FIG. 2A is a flow chart illustrating a method performed by a first network entity, in accordance with some embodiments of the present disclosure.
  • a method 200 is performed by a second network entity.
  • the method 200 comprises: a step S202, muting a notification of application status, when a condition is met; and/or a step S204, activating the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the application status may be about an application on a terminal device.
  • the application status may include a start or a stop of a traffic of the application.
  • FIG. 2B is a flow chart illustrating additional steps of the method shown in FIG. 2A.
  • the method 200 may further comprise: a step S206, transmitting to a first network entity a first message indicating the condition.
  • the first message may be a message for provisioning a policy and charging control, PCC, Rule.
  • the first message may comprise at least one of:a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the PCC rule may include the condition.
  • the first message may include at least one of:condition data for indicating the condition, or an indication about whether to mute the notification of application status or to activate the notification of application status.
  • the notification of application status may be transmitted from the first network entity to the second network entity, when the notification of application status is activated.
  • the first network entity may comprise a session management function, SMF, or a packet data network gateway control plane, PGW-C.
  • the second network entity may comprise a policy control function, PCF, or a policy and charging rules function, PCRF.
  • the application status may be obtained via a third network entity.
  • the third network entity may comprise a user plane function, UPF, or a packet data network gateway user plane, PGW-U.
  • the method 200 may further comprise: a step S208, transmitting to a first network entity a second message for muting the notification of application status.
  • the second message may be transmitted by the second network entity, when the second network entity determines that the condition is met.
  • the second message may be a message for modifying a session management policy.
  • the second message may comprise at least one of: a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the second message may include at least one of: an indication to mute the notification of application status, or condition data for indicating the condition.
  • the method 200 may further comprise: a step S210, transmitting to a first network entity a third message for activating the notification of application status.
  • the third message may be transmitted by the second network entity, when the second network entity determines that the condition is not met.
  • the third message may be a message for modifying a session management policy.
  • the third message may comprise at least one of: a response for policy control create, a response for policy control update, or a notification for policy control update.
  • the third message may include at least one of: an indication to activate the notification of application status, or condition data for indicating the condition.
  • the condition may comprise a time period.
  • the time period comprises a mute notification activation time and/or a mute notification deactivation time.
  • the condition may comprise an area.
  • the area may be where a terminal device is located.
  • the notification of application status is muted, based on whether the terminal device presence status is in the area or out of the area (i.e., based on based on PRA) .
  • the condition may comprise an occurrence of an event, and/or a subscription.
  • the method 200 may comprises any one or more of the additional steps S206, S208, S210.
  • the dynamic mute notification mechanism is proposed, and it could be implemented either by PCF controlled mute notification method or by conditioned mute notification method.
  • more flexible mute notification mechanism may be provided.
  • the notification may be muted dynamically, based on a specific condition. Therefore, the configuration about muting the notification may be modified, even during PCC rule life cycle.
  • the first example will be muting notification based on periodic time.
  • the PCF would provide relevant polices such as QoS and Bandwidth policy to the SMF, in order to better manage the network resource.
  • the PCF doesn’ t require the SMF to report such events, since the PCF doesn’ t take differentiated policy based on reported event. The relevant signallings among the PCF, the SMF and the UPF are avoided.
  • the first example will be muting notification based on PRA.
  • one PRA representing a shopping mall.
  • the SMF should report APP_START/APP_STOP to the PCF.
  • the PCF would provide relevant polices such as QoS and Bandwidth policy to the SMF, in order to provide better user experience.
  • the PCF doesn’ t require the SMF to report such events since the PCF doesn’ t take differentiated policy based on reported event. The relevant signallings among the PCF, the SMF and the UPF are avoided.
  • the PCF may control the muting of the notification. Mute Notification would be activated/deactivated by the PCF, based on dynamic information, such as ToD, PRA status or subscription change etc.
  • the PCF may update muteNotif in the TrafficControllData data structure in Npcf_SMPolicyControl_Update/UpdateNotify operation.
  • the SMF should start to report the application status to the PCF, in order to enforce policies based on current application status. To do this, the SMF notifies the UPF to do the application start or stop report by modifying the URR associated with the relevant PDRs for the application to provide start and stop notifications, or by provisioning a new URR provides start and stop notifications and associating that URR to the relevant PDRs.
  • SMF should not report application status to the PCF any longer, and it’s supposed that policies enforced in the SMF is applicable regardless of application status. To do this, the SMF notifies the UPF to stop the application start or stop report by modifying the URR associated with the relevant PDRs for the application, or by removing the association of the URR to the relevant PDRs.
  • the SMF needs not to determine whether the condition is met for muting notification.
  • periodic APP status report and periodic policy enforcement between the SMF and the PCF could NOT be avoided, even if the same behavior on the SMF and PCF are repeated.
  • Option 1 can be evolved to option 2 (conditioned mute notification method) to further reduce the signalling between SMF and PCF.
  • the Mute Notification would be controlled by the SMF, based on the condition data received from the PCF.
  • the PCF may provision SMF with condition data, for the SMF to decide at what time or in which PRA status the indication “muteNotif” would be changed.
  • the PCF shall provision a PCC rule and one reference to the TrafficControlData data structure within the "refTcData” attribute as defined in subclause 4.2.6.2.1 of 3GPP TS 29.512.
  • the “muteNotifCondData” attribute shall be included, in the TrafficControlData data structure as described in Table 5.6.2.10-1 of 3GPP TS 29.512. It shall include within its "refCondData” attribute the value of the "condId” attribute of the targeted ConditionData instance.
  • the PCF shall also ensure that this referenced ConditionData instance is included in the "conds" map attribute within the SmPolicyDecision data structure, following the procedures defined in subclause 4.2.6.1 of 3GPP TS 29.512.
  • the attribute “praInfos” may be included in ConditonData instance to indicate at which PRA status the mute notification is enforced.
  • the SMF notifies the UPF to do the application start or stop report by modifying the URR associated with the relevant PDRs for the application to provide start and stop notifications, or by provisioning a new URR that provides start and stop notifications and associating that URR to the relevant PDRs. Otherwise, the SMF notifies the UPF to stop the application start or stop report by modifying the URR associated with the relevant PDRs for the application, or by removing the association of the URR to the relevant PDRs.
  • FIG. 3 is a diagram showing exemplary messages and procedures for the proposed method, in accordance with some embodiments of the present disclosure.
  • the PCF 3 may update “muteNotif” in the TrafficControllData data structure in messages, Npcf_SMPolicyControl_Create Response (in alternative A) , Npcf_SMPolicyControl_Update Response (in alternative B) , Npcf_SMPolicyControl_UpdateNotify (in alternative C) .
  • the PCF 3 may directly indicate the SMF 1 to mute or not mute the notification.
  • condition data e.g., including activation time, deactivation time, PRA information, etc.
  • the SMF 1 may determine whether to mute the notification based on the condition data.
  • step A1 the SMF 1 transmits to PCF a message Npcf_SMPolicyControl_Create.
  • the PCF 3 transmits to SMF 1 a message Npcf_SMPolicyControl_Create Response, including (TrafficControlData (muteNotif, muteNotifCondData) , ConditionData (praInfos) ) , which are defined above in embodiments of the present disclosure.
  • step B1 SMF1 transmits to PCF3 a message Npcf_SMPolicyControl_Update. Then in step A2, PCF3 transmits to SMF1 a message Npcf_SMPolicyControl_Update Response, including (TrafficControlData (muteNotif, muteNotifCondData) , ConditionData (praInfos) ) , which are defined above in embodiments of the present disclosure.
  • step C1 PCF3 transmits to SMF1 a message Npcf_SMPolicyControl_UpdateNotify, including (TrafficControlData (muteNotif, muteNotifCondData) , ConditionData (praInfos) ) , which are defined above in embodiments of the present disclosure. Then, in step C2, SMF1 transmits to PCF3 a message Npcf_SMPolicyControl_UpdateNotify response.
  • SMF 1 when for some PCC rules, (as option 1) mute notification is changed directly, or (as option 2) it is determined by the SMF 1 that the condition for mute notification change is hit, SMF 1 notifies UPF 2 about the enabling or disabling of report of start and stop of traffic by adding or moving the triggers of "start of traffic” and "stop of traffic” in the URR associated with the PDRs corresponding to the PCC rules.
  • SMF 1 transmits to UPF 2 a message PFCP Session Modification Request (URR: Reporting Triggers (Start of Traffic, Stop of Traffic) . Then, UPF2 transmits to SMF1 a message PFCP Session Establishment Response.
  • UPF PFCP Session Modification Request
  • the traffic flows defined in 3GPP TS 23.502 may be improved by embodiments of the present disclosure.
  • FIG. 4A is a diagram showing detailed steps for a first exemplary procedure.
  • FIG. 4A is a diagram showing a procedure for SM policy association establishment, which is the same as Figure 4.16.4-1: SM Policy Association Establishment in 3GPP TS 23.502.
  • the PCF may provide muteNotificationData in TrafficControlData data structure (as in alternative A in FIG. 3) , which include the condition of mute notification: TOD or/and PRA info.
  • FIG. 4B is a diagram showing detailed steps for a second exemplary procedure.
  • FIG. 4B is a diagram showing a procedure for SMF initiated SM policy association modification, which is the same as Figure 4.16.5.1-1: SMF initiated SM Policy Association Modification in 3GPP TS 23.502.
  • PCF may update policies based on APP_START or APP_STOP reported from the SMF. Additionally, the PCF may update the following attribute to the SMF (as in alternative B in FIG. 3) : “muteNotif” , and/or “muteNotificationData” in TrafficControlData data structure.
  • FIG. 4C is a diagram showing detailed steps for a third exemplary procedure.
  • FIG. 4C is a diagram showing a procedure for PCF initiated SM policy association modification, which is the same as Figure 4.16.5.2-1: PCF initiated SM Policy Association Modification in 3GPP TS 23.502.
  • PCF may update policies based on APP_START or APP_STOP reported from the SMF. Additionally, the PCF may update the following attribute to the SMF (as in alternative C in FIG. 3) : “muteNotif” , and/or “muteNotificationData” in TrafficControlData data structure.
  • a Mute-Notification-Condition AVP (Attribute-Value Pair) may be added in Charging-Rule-Definition as in following table.
  • Mute-Notification-Condition AVP may include parameters as in following table.
  • IP-CAN Session Establishment (such as step 3 with CCR-I, step 14 with CCA-I) ; Figure 7.4 IP-CAN Session Modification; GW (PCEF) initiated (such as step 5 with Gx CCR-U, step 17 with Gx CCA-U) ; and Figure 7.5 IP-CAN Session Modification; PCRF initiated (such as step 12 with Gx RAR, step 18 with Gx RAA) , in 3GPP TS 23.203 v17.2.0.
  • PCEF IP-CAN Session Modification
  • PCRF initiated (such as step 12 with Gx RAR, step 18 with Gx RAA) , in 3GPP TS 23.203 v17.2.0.
  • Gx means the interference.
  • CCR-I is a credit control request-initial command
  • CCA-I is a credit control answer-initial command
  • CCR-U is a credit control request-update command
  • CCA-U is a credit control answer-update command
  • RAR is a Re-Auth-Request command
  • RAA is a Re-Auth-Answer command.
  • the first message, second message, third message for indicating a condition, or for directly muting/activating the notification may comprise: Gx CCR-I/CCA-I message in Figure 7.2-1 in 3GPP TS 23.203 v17.2.0; Gx RAR/RAA message in Figure 7.5 in 3GPP TS 23.203 v17.2.0, Gx CCR-U/CCA-U message in Figure 7.4 in 3GPP TS 23.203 v17.2.0.
  • FIG. 5A is a diagram showing detailed steps for a fourth exemplary procedure.
  • FIG. 5A is a diagram showing a procedure for IP-CAN Session Establishment, which is the same as Figure 7.2-1 IP-CAN Session Establishment in 3GPP TS 23.203 v17.2.0.
  • step 3 the GW (PCEF) transmits an indication of IP CAN session Establishment to a H-PCRF.
  • H-PCRF transmits to the GW (PCEF) an Acknowledge IP CAN Session Establishment, with Mute-Notification AVP and/or Mute-Notification-Condition AVP, which may include indication about whether to mute the notification and/or the condition of mute notification: TOD or/and PRA info.
  • FIG. 5B is a diagram showing detailed steps for a fifth exemplary procedure.
  • FIG. 5B is a diagram showing a procedure for IP-CAN Session Modification, which is the same as Figure 7.4 IP-CAN Session Modification; GW (PCEF) initiated in 3GPP TS 23.203 v17.2.0.
  • GW transmits to H-PCRF an indication of IP-CAN Session modification.
  • H-PCRF transmits to GW (PCEF) an Acknowledge IP CAN Session Modification, with Mute-Notification AVP and/or Mute-Notification-Condition AVP, which may include indication about whether to mute the notification and/or the condition of mute notification: TOD or/and PRA info.
  • FIG. 5C is a diagram showing detailed steps for a sixth exemplary procedure.
  • FIG. 5C is a diagram showing a procedure for IP-CAN Session Modification, which is the same as Figure 7.5 IP-CAN Session Modification; PCRF initiated in 3GPP TS 23.203 v17.2.0.
  • H-PCRF transmits to GW (PCEF) a Policy and Charging Rules Provision, with Mute-Notification AVP and/or Mute-Notification-Condition AVP, which may include indication about whether to mute the notification and/or the condition of mute notification: TOD or/and PRA info.
  • PCEF Policy and Charging Rules Provision
  • Mute-Notification AVP and/or Mute-Notification-Condition AVP may include indication about whether to mute the notification and/or the condition of mute notification: TOD or/and PRA info.
  • GW (PCEF) transmits acknowledgement to H-PCRF.
  • FIG. 6 is a block diagram showing an exemplary apparatus for a first network entity, which is suitable for perform the method according to embodiments of the disclosure.
  • an apparatus 60 for a first network entity in a communication network comprises: a processor 602; and a memory 604.
  • the memory contains instructions executable by the processor.
  • the apparatus for the first network entity is operative for: muting a notification of application status, when a condition is met; and/or activating the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the apparatus 60 is further operative to perform the method according to any of the above embodiments, such as these shown in FIG. 1A, 1B.
  • FIG. 7 is a block diagram showing an exemplary apparatus for a second network entity, which is suitable for perform the method according to embodiments of the disclosure.
  • an apparatus 70 for a second network entity in a communication network comprises: a processor 702; and a memory 704.
  • the memory contains instructions executable by the processor.
  • the apparatus for the second network entity is operative for: muting a notification of application status, when a condition is met; and/or activating the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the apparatus 70 is further operative to perform the method according to any of the above embodiments, such as these shown in FIG. 2A, 2B.
  • the processors 602, 702 may be any kind of processing component, such as one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs) , special-purpose digital logic, and the like.
  • the memories 604, 704 may be any kind of storage component, such as read-only memory (ROM) , random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • FIG. 8 is a block diagram showing an apparatus/computer readable storage medium, according to embodiments of the present disclosure.
  • the computer-readable storage medium 80 or any other kind of product, storing instructions 801 which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the above embodiments, such as these shown in FIG. 1A, 1B, 2A, 2B.
  • the present disclosure may also provide a carrier containing the computer program as mentioned above, the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • the computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory) , a ROM (read only memory) , Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.
  • FIG. 9A is a block diagram showing units of an exemplary apparatus for a first network entity, which is suitable for perform the method according to embodiments of the disclosure.
  • an apparatus 91 for a first network entity in a communication network comprises: a muting unit 912, configured to mute a notification of application status, when a condition is met; and/or an activating unit 914, configured to activate the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the apparatus 91 is further operative to perform the method according to any of the above embodiments, such as these shown in FIG. 1A, 1B.
  • FIG. 9B is a block diagram showing units of an exemplary apparatus for a third network entity, which is suitable for perform the method according to embodiments of the disclosure.
  • an apparatus 92 for a third network entity in a communication network comprises: a muting unit 922, configured to mute a notification of application status, when a condition is met; and/or an activating unit 924, configured to activate the notification of application status, when the condition is not met.
  • the condition may be a mute notification condition.
  • the apparatus 92 is further operative to perform the method according to any of the above embodiments, such as these shown in FIG. 2A, 2B.
  • unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • the apparatus may not need a fixed processor or memory, any kind of computing resource and storage resource may be arranged from at least one network node/device/entity/apparatus relating to the communication system.
  • the virtualization technology and network computing technology e.g., cloud computing
  • an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses) , firmware (one or more apparatuses) , software (one or more modules/units) , or combinations thereof.
  • firmware or software implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.
  • FIG. 10 shows an example of a communication system 1000 in accordance with some embodiments.
  • the communication system 1000 includes a telecommunication network 1002 that includes an access network 1004, such as a radio access network (RAN) , and a core network 1006, which includes one or more core network nodes 1008.
  • the access network 1004 includes one or more access network nodes, such as network nodes 1010a and 1010b (one or more of which may be generally referred to as network nodes 1010) , or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes 1010 facilitate direct or indirect connection of user equipment (UE) , such as by connecting UEs 1012a, 1012b, 1012c, and 1012d (one or more of which may be generally referred to as UEs 1012) to the core network 1006 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1000 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 1000 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1012 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1010 and other communication devices.
  • the network nodes 1010 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1012 and/or with other network nodes or equipment in the telecommunication network 1002 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1002.
  • the core network 1006 connects the network nodes 1010 to one or more hosts, such as host 1016. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1006 includes one more core network nodes (e.g., core network node 1008) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1008.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC) , Mobility Management Entity (MME) , Home Subscriber Server (HSS) , Access and Mobility Management Function (AMF) , Session Management Function (SMF) , Authentication Server Function (AUSF) , Subscription Identifier De-concealing function (SIDF) , Unified Data Management (UDM) , Security Edge Protection Proxy (SEPP) , Network Exposure Function (NEF) , and/or a User Plane Function (UPF) .
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1016 may be under the ownership or control of a service provider other than an operator or provider of the access network 1004 and/or the telecommunication network 1002, and may be operated by the service provider or on behalf of the service provider.
  • the host 1016 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 1000 of FIG. 10 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM) ; Universal Mobile Telecommunications System (UMTS) ; Long Term Evolution (LTE) , and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G) ; wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi) ; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax) , Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile T
  • the telecommunication network 1002 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1002 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1002. For example, the telecommunications network 1002 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC) /Massive IoT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 1012 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1004.
  • a UE may be configured for operating in single-or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC) , such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio –Dual Connectivity (EN-DC) .
  • MR-DC multi-radio dual connectivity
  • the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012c and/or 1012d) and network nodes (e.g., network node 1010b) .
  • the hub 1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1014 may be a broadband router enabling access to the core network 1006 for the UEs.
  • the hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1014 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1014 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1014 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub 1014 may have a constant/persistent or intermittent connection to the network node 1010b.
  • the hub 1014 may also allow for a different communication scheme and/or schedule between the hub 1014 and UEs (e.g., UE 1012c and/or 1012d) , and between the hub 1014 and the core network 1006.
  • the hub 1014 is connected to the core network 1006 and/or one or more UEs via a wired connection.
  • the hub 1014 may be configured to connect to an M2M service provider over the access network 1004 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1010 while still connected via the hub 1014 via a wired or wireless connection.
  • the hub 1014 may be a dedicated hub –that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1010b.
  • the hub 1014 may be a non-dedicated hub –that is, a device which is capable of operating to route communications between the UEs and network node 1010b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 11 shows a UE 1100 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA) , wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , smart device, wireless customer-premise equipment (CPE) , vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LME laptop-embedded equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP) , including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC) , vehicle-to-vehicle (V2V) , vehicle-to-infrastructure (V2I) , or vehicle-to-everything (V2X) .
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller) .
  • a UE may
  • the UE 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/output interface 1106, a power source 1108, a memory 1110, a communication interface 1112, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in FIG. 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 1102 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1110.
  • the processing circuitry 1102 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs) , application specific integrated circuits (ASICs) , etc. ) ; programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP) , together with appropriate software; or any combination of the above.
  • the processing circuitry 1102 may include multiple central processing units (CPUs) .
  • the input/output interface 1106 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 1100.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 1108 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet) , photovoltaic device, or power cell, may be used.
  • the power source 1108 may further include power circuitry for delivering power from the power source 1108 itself, and/or an external power source, to the various parts of the UE 1100 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1108.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1108 to make the power suitable for the respective components of the UE 1100 to which power is supplied.
  • the memory 1110 may be or be configured to include memory such as random access memory (RAM) , read-only memory (ROM) , programmable read-only memory (PROM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1110 includes one or more application programs 1114, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1116.
  • the memory 1110 may store, for use by the UE 1100, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1110 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID) , flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM) , synchronous dynamic random access memory (SDRAM) , external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs) , such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC) , integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card. ’
  • the memory 1110 may allow the UE 1100 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1110, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1102 may be configured to communicate with an access network or other network using the communication interface 1112.
  • the communication interface 1112 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1122.
  • the communication interface 1112 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network) .
  • Each transceiver may include a transmitter 1118 and/or a receiver 1120 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth) .
  • the transmitter 1118 and receiver 1120 may be coupled to one or more antennas (e.g., antenna 1122) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1112 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA) , Wideband Code Division Multiple Access (WCDMA) , GSM, LTE, New Radio (NR) , UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP) , synchronous optical networking (SONET) , Asynchronous Transfer Mode (ATM) , QUIC, Hypertext Transfer Protocol (HTTP) , and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Universal Mobile communications
  • WiMax Ethernet
  • TCP/IP transmission control protocol/internet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 1112, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature) , random (e.g., to even out the load from reporting from several sensors) , in response to a triggering event (e.g., when moisture is detected an alert is sent) , in response to a request (e.g., a user initiated request) , or a continuous stream (e.g., a live video feed of a patient) .
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR) , a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal-or
  • AR Augmented
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG. 12 shows a network node 1200 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points) , base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)) .
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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 controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs) , sometimes referred to as Remote Radio Heads (RRHs) .
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS) .
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs) , Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs) ) , and/or Minimization of Drive Tests (MDTs) .
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location
  • the network node 1200 includes a processing circuitry 1202, a memory 1204, a communication interface 1206, and a power source 1208.
  • the network node 1200 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc. ) , which may each have their own respective components.
  • the network node 1200 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1200 may be configured to support multiple radio access technologies (RATs) .
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1204 for different RATs) and some components may be reused (e.g., a same antenna 1210 may be shared by different RATs) .
  • the network node 1200 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1200, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1200.
  • RFID Radio Frequency Identification
  • the processing circuitry 1202 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1200 components, such as the memory 1204, to provide network node 1200 functionality.
  • the processing circuitry 1202 includes a system on a chip (SOC) .
  • the processing circuitry 1202 includes one or more of radio frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214.
  • the radio frequency (RF) transceiver circuitry 1212 and the baseband processing circuitry 1214 may be on separate chips (or sets of chips) , boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 1212 and baseband processing circuitry 1214 may be on the same chip or set of chips, boards, or units.
  • the memory 1204 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM) , read-only memory (ROM) , mass storage media (for example, a hard disk) , removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD) ) , and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1202.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM) , read-only memory (ROM) , mass storage media (for example, a hard disk) , removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Dis
  • the memory 1204 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1202 and utilized by the network node 1200.
  • the memory 1204 may be used to store any calculations made by the processing circuitry 1202 and/or any data received via the communication interface 1206.
  • the processing circuitry 1202 and memory 1204 is integrated.
  • the communication interface 1206 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1206 comprises port (s) /terminal (s) 1216 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1206 also includes radio front-end circuitry 1218 that may be coupled to, or in certain embodiments a part of, the antenna 1210. Radio front-end circuitry 1218 comprises filters 1220 and amplifiers 1222.
  • the radio front-end circuitry 1218 may be connected to an antenna 1210 and processing circuitry 1202.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1210 and processing circuitry 1202.
  • the radio front-end circuitry 1218 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1218 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1220 and/or amplifiers 1222.
  • the radio signal may then be transmitted via the antenna 1210.
  • the antenna 1210 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1218.
  • the digital data may be passed to the processing circuitry 1202.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1200 does not include separate radio front-end circuitry 1218, instead, the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210.
  • the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210.
  • all or some of the RF transceiver circuitry 1212 is part of the communication interface 1206.
  • the communication interface 1206 includes one or more ports or terminals 1216, the radio front-end circuitry 1218, and the RF transceiver circuitry 1212, as part of a radio unit (not shown) , and the communication interface 1206 communicates with the baseband processing circuitry 1214, which is part of a digital unit (not shown) .
  • the antenna 1210 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1210 may be coupled to the radio front-end circuitry 1218 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1210 is separate from the network node 1200 and connectable to the network node 1200 through an interface or port.
  • the antenna 1210, communication interface 1206, and/or the processing circuitry 1202 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1210, the communication interface 1206, and/or the processing circuitry 1202 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1208 provides power to the various components of network node 1200 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component) .
  • the power source 1208 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1200 with power for performing the functionality described herein.
  • the network node 1200 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1208.
  • the power source 1208 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 1200 may include additional components beyond those shown in FIG. 12 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 1200 may include user interface equipment to allow input of information into the network node 1200 and to allow output of information from the network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1200.
  • FIG. 13 is a block diagram of a host 1300, which may be an embodiment of the host 1016 of FIG. 10, in accordance with various aspects described herein.
  • the host 1300 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1300 may provide one or more services to one or more UEs.
  • the host 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a network interface 1308, a power source 1310, and a memory 1312.
  • processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a network interface 1308, a power source 1310, and a memory 1312.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 11 and 12, such that the descriptions thereof are generally applicable to the corresponding components of host 1300.
  • the memory 1312 may include one or more computer programs including one or more host application programs 1314 and data 1316, which may include user data, e.g., data generated by a UE for the host 1300 or data generated by the host 1300 for a UE. Embodiments of the host 1300 may utilize only a subset or all of the components shown.
  • the host application programs 1314 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC) , High Efficiency Video Coding (HEVC) , Advanced Video Coding (AVC) , MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC) , MPEG, G.
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG MPEG
  • VP9 video codecs
  • audio codecs e.g., FLAC, Advanced Audio Coding (AAC)
  • the host application programs 1314 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1300 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1314 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP) , Real-Time Streaming Protocol (RTSP) , Dynamic Adaptive Streaming over HTTP (MPEG-DASH) , etc.
  • HTTP Live Streaming HLS
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc. ) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1404 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs) ) , provide VMs 1408a and 1408b (one or more of which may be generally referred to as VMs 1408) , and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to the VMs 1408.
  • the VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406.
  • a virtualization layer 1406 Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV) .
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1408, and that part of hardware 1404 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1408 on top of the hardware 1404 and corresponds to the application 1402.
  • Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1410, which, among others, oversees lifecycle management of applications 1402.
  • hardware 1404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1412 which may alternatively be used for communication between hardware nodes and radio units.
  • FIG. 15 shows a communication diagram of a host 1502 communicating via a network node 1504 with a UE 1506 over a partially wireless connection in accordance with some embodiments.
  • UE such as a UE 1012a of FIG. 10 and/or UE 1100 of FIG. 11
  • network node such as network node 1010a of FIG. 10 and/or network node 1200 of FIG. 12
  • host such as host 1016 of FIG. 10 and/or host 1300 of FIG. 13
  • host 1502 Like host 1300, embodiments of host 1502 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1502 also includes software, which is stored in or accessible by the host 1502 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1506 connecting via an over-the-top (OTT) connection 1550 extending between the UE 1506 and host 1502.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 1550.
  • the network node 1504 includes hardware enabling it to communicate with the host 1502 and UE 1506.
  • the connection 1560 may be direct or pass through a core network (like core network 1006 of FIG. 10) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 1006 of FIG. 10
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1506 includes hardware and software, which is stored in or accessible by UE 1506 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1506 with the support of the host 1502.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1506 with the support of the host 1502.
  • an executing host application may communicate with the executing client application via the OTT connection 1550 terminating at the UE 1506 and host 1502.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1550 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • the OTT connection 1550 may extend via a connection 1560 between the host 1502 and the network node 1504 and via a wireless connection 1570 between the network node 1504 and the UE 1506 to provide the connection between the host 1502 and the UE 1506.
  • the connection 1560 and wireless connection 1570, over which the OTT connection 1550 may be provided, have been drawn abstractly to illustrate the communication between the host 1502 and the UE 1506 via the network node 1504, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1502 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1506.
  • the user data is associated with a UE 1506 that shares data with the host 1502 without explicit human interaction.
  • the host 1502 initiates a transmission carrying the user data towards the UE 1506.
  • the host 1502 may initiate the transmission responsive to a request transmitted by the UE 1506. The request may be caused by human interaction with the UE 1506 or by operation of the client application executing on the UE 1506.
  • the transmission may pass via the network node 1504, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1512, the network node 1504 transmits to the UE 1506 the user data that was carried in the transmission that the host 1502 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1514, the UE 1506 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1506 associated with the host application executed by the host 1502.
  • the UE 1506 executes a client application which provides user data to the host 1502.
  • the user data may be provided in reaction or response to the data received from the host 1502.
  • the UE 1506 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1506. Regardless of the specific manner in which the user data was provided, the UE 1506 initiates, in step 1518, transmission of the user data towards the host 1502 via the network node 1504.
  • the network node 1504 receives user data from the UE 1506 and initiates transmission of the received user data towards the host 1502.
  • the host 1502 receives the user data carried in the transmission initiated by the UE 1506.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1506 using the OTT connection 1550, in which the wireless connection 1570 forms the last segment.
  • an improved manner for muting a notification of application status may be provided.
  • embodiments of the present disclosure may provide a more flexible mute notification mechanism. A certain amount of signaling for muting the notification may be reduced and it will contribute to energy consumption reduction in the communication network. More precisely, the teachings of these embodiments may improve the performance, e.g., data rate, latency, power consumption, of the communication network, and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime.
  • factory status information may be collected and analyzed by the host 1502.
  • the host 1502 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1502 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights) .
  • the host 1502 may store surveillance video uploaded by a UE.
  • the host 1502 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1502 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices) , or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1502 and/or UE 1506.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1550 may include message format, retransmission settings, preferred routing etc. ; the reconfiguring need not directly alter the operation of the network node 1504. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1502.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1550 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente invention concernent un procédé et un appareil pour la mise en sourdine d'une notification d'état d'application. Le procédé mis en œuvre par une première entité de réseau comprend les étapes consistant à : mettre en sourdine (S102) une notification d'un état d'application, lorsqu'une condition est satisfaite; et/ou activer (S104) la notification d'état d'application, lorsque la condition n'est pas satisfaite. Un mécanisme de notification en sourdine plus flexible peut être fourni. Selon des modes de réalisation de la présente invention, la notification peut être mise en sourdine de manière dynamique, sur la base d'une condition spécifique. Par conséquent, la configuration concernant la mise en sourdine de la notification peut être modifiée, même pendant un cycle de vie de règle PCC.
PCT/CN2023/082167 2022-03-25 2023-03-17 Procédé et appareil pour la mise en sourdine de notification d'état d'application WO2023179483A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN2022083126 2022-03-25
CNPCT/CN2022/083126 2022-03-25
CN2022084796 2022-04-01
CNPCT/CN2022/084796 2022-04-01

Publications (2)

Publication Number Publication Date
WO2023179483A1 WO2023179483A1 (fr) 2023-09-28
WO2023179483A9 true WO2023179483A9 (fr) 2023-11-16

Family

ID=88099902

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/082167 WO2023179483A1 (fr) 2022-03-25 2023-03-17 Procédé et appareil pour la mise en sourdine de notification d'état d'application

Country Status (1)

Country Link
WO (1) WO2023179483A1 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101744750B1 (ko) * 2013-03-28 2017-06-09 가부시키가이샤 코나미 데지타루 엔타테인멘토 관리 장치, 관리 방법 및 기억 매체
CN108124058A (zh) * 2017-12-19 2018-06-05 北京小米移动软件有限公司 信息显示控制方法及装置
CN113709026B (zh) * 2021-08-04 2022-11-04 青岛海信移动通信技术股份有限公司 即时通信消息的处理方法、设备、存储介质和程序产品

Also Published As

Publication number Publication date
WO2023179483A1 (fr) 2023-09-28

Similar Documents

Publication Publication Date Title
WO2022248118A1 (fr) Autorisation de fonctions de réseau de consommateur
WO2023016280A1 (fr) Procédés et appareils pour service d'application de périphérie
WO2023143806A1 (fr) Mise à jour d'indicateur de routage par l'intermédiaire d'une procédure de mise à jour de paramètres d'ue (upu)
WO2023058009A1 (fr) Indication d'itinérance en cas de catastrophe pour session et politique
WO2023179483A9 (fr) Procédé et appareil pour la mise en sourdine de notification d'état d'application
WO2024027839A9 (fr) Procédé et appareil de configuration de type de rapport d'emplacement
WO2024027838A1 (fr) Procédé et appareil pour arrêter un rapport de localisation
WO2023185737A1 (fr) Procédé et appareil permettant d'effectuer une authentification/autorisation secondaire pour un dispositif terminal dans un réseau de communication
WO2023206238A1 (fr) Procédé et appareil de configuration dynamique de tranche dans un réseau de communication
WO2024138654A1 (fr) Pause de facturation de smf
WO2024130482A1 (fr) Procédé et appareil de gestion de canal de données pour dispositif terminal
WO2024032571A1 (fr) Procédé et appareil aux fins d'une sélection de fonction de plan d'utilisateur
WO2023122972A1 (fr) Procédé et appareil permettant de maintenir une session active dans un réseau de communication
WO2024099090A1 (fr) Procédé et appareil de configuration d'événement au niveau d'un équipement terminal
WO2023168657A1 (fr) Procédé et appareil de sélection de port de lag pour un flux d'ip
WO2024040388A1 (fr) Procédé et appareil de transmission de données
WO2023143314A1 (fr) Procédé et appareil de configuration de qos dans un réseau de communication
WO2023142676A1 (fr) Élimination d'autorisation spécifique à un service dans un cœur de réseau 5g (5gc)
WO2023011942A1 (fr) Rapport de relaxation de mesure radio précoce
WO2023014264A1 (fr) Réduction de rapports de relaxation de mesure radio inutile
WO2023117829A1 (fr) Procédé et appareil de mise à jour d'informations de liaison dans réseau de communication
WO2024069477A1 (fr) Transfert de rapport de cellule pscell réussi
WO2024030059A1 (fr) Mesure de qualité d'expérience
WO2023198733A1 (fr) Détermination efficace d'informations d'abonnement d'utilisateur dans un réseau multi-domaine
WO2023180115A1 (fr) Procédés d'exposition de données/analyse d'un réseau de communication dans des scénarios d'itinérance

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23773731

Country of ref document: EP

Kind code of ref document: A1