WO2020222036A1 - Critères de filtrage initial dynamique (ifc) dans un sous-système multimédia de protocole internet (ims) dans des réseaux de 5e génération - Google Patents

Critères de filtrage initial dynamique (ifc) dans un sous-système multimédia de protocole internet (ims) dans des réseaux de 5e génération Download PDF

Info

Publication number
WO2020222036A1
WO2020222036A1 PCT/IB2019/053611 IB2019053611W WO2020222036A1 WO 2020222036 A1 WO2020222036 A1 WO 2020222036A1 IB 2019053611 W IB2019053611 W IB 2019053611W WO 2020222036 A1 WO2020222036 A1 WO 2020222036A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
application server
node
server node
dynamic application
Prior art date
Application number
PCT/IB2019/053611
Other languages
English (en)
Inventor
Ankur DAUNERIA
George Foti
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)
Priority to PCT/IB2019/053611 priority Critical patent/WO2020222036A1/fr
Publication of WO2020222036A1 publication Critical patent/WO2020222036A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding

Definitions

  • 3GPP TS 23.501vl6.0.2 is illustrated in FIG. 1.
  • the 5G System architecture includes the following network functions (NF):
  • AMF Access and Mobility Management Function
  • DN Data Network
  • operator services e.g. operator services, Internet access or 3rd party
  • NSSF Network Slice Selection Function
  • PCF Policy Control Function
  • SMF Session Management Function
  • SEPP Security Edge Protection Proxy
  • NWDAF Network Data Analytics Function
  • a network function may correspond to a 3 GPP adopted or 3GPP defined processing function in a network that has defined functional behavior and defined 3 GPP interfaces.
  • a network slice may correspond to a logical network that provides specific network capabilities and network characteristics.
  • a network slice instance may correspond to a set of network function instances and the required resources (e.g., compute, storage, and networking resources) which form a deployed network slice.
  • a network exposure may correspond to 5G networks that allows network exposure to external or internal customer as described in wireless communication standards such as in 3GPP TS 23.502.
  • the network capability exposure includes:
  • Businesses as part of different verticals may bring in additional wireless devices into 5G, i.e., New Radio (NR), networks.
  • Industry verticals may generally refer to a company that may offer a product or service that may fit into various industries.
  • human and network connected machines may interact using operator enabled communication services in different use cases in 5G networks.
  • different industry verticals joining the 5G ecosystem may bring in new use cases to which telecom operators may provide their
  • a large volume of wireless devices with call capabilities may be part of the 5G ecosystem for supporting different verticals or industries in different roles and capacities.
  • a machine-to-machine (M2M) device such as an automobile can be used by multiple users supporting different business at different time and places.
  • Some embodiments advantageously provide a method and system for dynamic linking of an application server node for modifying at least one characteristic of a communication session.
  • a wireless device configured with a predefined subscriber profile that identifies an application server node to link to a communication session.
  • the wireless device includes processing circuitry configured to participate in the session where the session is linked with a dynamic application server node that is unidentified by the predefined subscriber profile and where the dynamic application server node is linked to the session based at least in part on a session context of the session.
  • the dynamic application server node is configured to modify at least one characteristic of the session.
  • the at least one characteristic includes at least one of a call display and call forwarding to a different target device than an original target device.
  • the processing circuitry is configured to, during initiation of the session, determine a session context of the session.
  • the processing circuitry is further configured to cause transmission of a session initiation protocol, SIP, invite to initiate the session where the SIP invite identifies the dynamic application server node to link to the communication session.
  • the SIP invite identifies the dynamic application server node by including a fully qualified domain name of the dynamic application server node in the SIP invite.
  • the linking of the dynamic application server node is on a per session basis.
  • the dynamic application server node is linked to the session via a proxy application server node.
  • the session context corresponds to an inclusion of an application server Fully Qualified Domain Name, FQDN, in session initiation protocol INVITE signaling.
  • a node for communication with a wireless device configured with a predefined subscriber profile that identifies an application server node to link to a session.
  • the node includes processing circuitry configured to receive signaling to initiate a session, and link a dynamic application server node with the session where the dynamic application server node is unidentified by the predefined subscriber profile and is linked based at least in part on a session context of the session.
  • the session initiation signaling identifies the dynamic application server node by a fully qualified domain name of the dynamic application server node. According to one or more embodiments of this aspect, the session initiation signaling identifies the dynamic application server node by a fully qualified domain name of the dynamic application server node. According to one or more
  • the processing circuitry is further configured to determine the session context of the session, determine the dynamic application server node to link to the session based at least in part on the session context of the session, and determine a fully qualified domain name of the dynamic application server node for linking to the session.
  • the session context corresponds to an inclusion of an application server Fully Qualified Domain Name, FQDN, in session initiation protocol INVITE signaling.
  • the linking of the dynamic application server node to the session includes temporarily modifying the predefined subscriber profile for the session to link the dynamic application server node.
  • node corresponds to a serving call session control function, S-CSCF, node.
  • the dynamic application server node is configured to modify at least one characteristics of the session.
  • the at least one characteristic includes at least one of a call display and call forwarding to a different target device than an original target device.
  • the linking of the dynamic application server node is on a per session basis.
  • the dynamic application server node is linked to the session via a proxy application server node.
  • the session initiation signaling corresponds to a session initiation protocol, SIP, invite message for initiating an internet protocol multimedia subsystem, IMS, session.
  • a method implemented in a wireless device configured with a predefined subscriber profile that identifies an application server node to link to a communication session. Participation in the session occurs where the session is linked with a dynamic application server node that is unidentified by the predefined subscriber profile, and where the dynamic application server node is linked to the session based at least in part on a session context of the session.
  • the dynamic application server node is configured to modify at least one characteristic of the session.
  • the at least one characteristic includes at least one of a call display and call forwarding to a different target device than an original target device.
  • a session context of the session is determined.
  • transmission of a session initiation protocol, SIP, invite to initiate the session is caused where the SIP invite identifying the dynamic application server node to link to the communication session.
  • the SIP invite identifies the dynamic application server node by including a fully qualified domain name of the dynamic application server node in the SIP invite.
  • the linking of the dynamic application server node is on a per session basis.
  • the dynamic application server node is linked to the session via a proxy application server node.
  • the session context is a per session basis.
  • a method implemented in a node for communication with a wireless device configured with a predefined subscriber profile that identifies an application server node to link to a session is provided. Signaling to initiate a session is received. A dynamic application server node is linked with the session where the dynamic application server node is unidentified by the predefined subscriber profile and is linked based at least in part on a session context of the session. According to one or more embodiments of this aspect, the session initiation signaling identifies the dynamic application server node by a fully qualified domain name of the dynamic application server node.
  • the session context of the session is determined.
  • the dynamic application server node to link to the session is determined based at least in part on the session context of the session.
  • a fully qualified domain name of the dynamic application server node for linking to the session is determined.
  • the session context corresponds to an inclusion of an application server Fully Qualified Domain Name, FQDN, in session initiation protocol INVITE signaling.
  • the linking of the dynamic application server node to the session includes temporarily modifying the predefined subscriber profile for the session to link the dynamic application server node.
  • node corresponds to a serving call session control function, S-CSCF, node.
  • the dynamic application server node is configured to modify at least one characteristics of the session.
  • the at least one characteristic includes at least one of a call display and call forwarding to a different target device than an original target device.
  • the linking of the dynamic application server node is on a per session basis.
  • the dynamic application server node is linked to the session via a proxy application server node.
  • the session initiation signaling corresponds to a session initiation protocol, SIP, invite message for initiating an internet protocol multimedia subsystem, IMS, session.
  • FIG. 1 is a block diagram of 5G system architecture
  • FIG. 2 is a diagram of various use cases
  • FIG. 3 is another diagram of various use cases
  • FIG. 4 is a block diagram of a system in accordance with the principles of the disclosure.
  • FIG. 5 is a flowchart of a process for participating in a session in accordance with the principles of the disclosure
  • FIG. 6 is a flowchart of a process based on context aware information in accordance with the principles of the disclosure
  • FIG. 7 is a flowchart of a process for linking an application server node in accordance with the principles of the disclosure.
  • FIG. 8 is a flowchart of a process for updating a SIP invite in accordance with the principles of the disclosure
  • FIGS. 9a- 9b are signaling diagrams of a process for dynamically linking an application server in accordance with the principles of the disclosure.
  • FIG. 10 is a diagram of a connected car/taxi use case in accordance with the principles of the disclosure.
  • FIG. 11 is another diagram of a connected car/vehicle use case in accordance with the principles of the disclosure.
  • FIG. 12 is a diagram of a connected bus use case in accordance with the principles of the disclosure;
  • FIG. 13 is a diagram of a connected self-driving train use case in accordance with the principles of the disclosure.
  • FIG. 14 is a diagram of a drone use case in accordance with the principles of the disclosure.
  • industry verticals transportation industry, logistic industry, etc. managing a large volume of wireless devices with 5 th generation (5G, also referred to as New Radio (NR)) operator supported call capabilities in different business use cases may need the functionality to influence the communications to adapt one or more characteristics of the communication such as to adapt displays and call forwarding depending on context, which is not provided in existing systems.
  • 5G also referred to as New Radio (NR)
  • NR New Radio
  • FIG. 2 I. Context Aware Caller Identification in different industry verticals (transportation industry, logistic industry, etc.) supporting different business use cases are illustrated in FIG. 2.
  • a self-driving tourist bus 2 i.e., type of wireless device or having wireless device capability
  • a self-driving taxi 6 i.e., type of wireless device or having wireless device capability
  • a wireless device 4 associated with its customer after reaching a location.
  • self-driving logistic vehicle 8 may make a call to a wireless device 4 associated with an administrator during a trip.
  • an unmanned aerial vehicle (UAV or drone) 10 i.e., type of wireless device or having wireless device capability
  • UAV or drone 10 may call a wireless device 4 associated with a customer in order for a customer to accept delivery of an E- commerce product (e.g. pizza) when the UAV 10 reaches a destination.
  • a self-driving train 12 i.e., type of wireless device or having wireless device capability
  • a self-driving taxi 6 calls wireless device 4 associated with its customer after reaching the pickup location where business verticals today cannot influence Caller ID displayed on display 5 in call setup to adapt to the rental vehicle business context as illustrated in FIG. 3.
  • a self-driving vehicle 14 i.e., connected car
  • Business verticals in existing systems cannot adapt the Caller ID to reflect the non-working status of otherwise working vehicles 14.
  • vehicle 14 may be used by different employers associated with different businesses across verticals for different hours as illustrated in FIG. 3. As illustrated in FIG.
  • a self-driving bus 2 calls wireless device 4 that is associated with a passenger of the self-driving bus 2.
  • the self-driving bus 2 is making the call to inform the passenger that the bus 2 is about to depart.
  • Business verticals in existing system in this use case are not able to adapt the Caller ID, as illustrated in FIG. 3, such as per a specific route (School route, Factory route) context based on business.
  • a single wireless device may follow different mobility patterns at different times (supporting different employers in different businesses across verticals) as illustrated in FIG. 3, but one or more characteristics of the
  • communication session such as caller ID displayed on display 5 may remain the same, irrespective of the varying session context, i.e., varying situation and/or purpose of the call.
  • a self-driving train 12 is calling wireless device 4 that is associated with one of its passengers to report to train 12 as it about to depart the station.
  • Business verticals in existing system are not able to adapt one or more characteristics of the communication session, as illustrated in FIG. 3, such as a modification to the Caller ID to personalize the call displays using the reservation details context.
  • a drone (UAV) 10 is calling wireless device 4 associated with a customer in order for the customer to accept delivering of the e- commerce product/pizza as the drone 10 reaches the destination.
  • Businesses verticals in existing systems are not able to adapt one or more characteristics of the communication session, as illustrated in FIG. 3, such as the Caller ID based on the delivery context (e.g., 15 minute delivery, 30 minute delivery) from the time pizza order is placed online until the time when the call is received from drone 10 after reaching the customer location.
  • a single user today can be associated with multiple wireless devices (e.g., smartphone, home phone, connected car, work phone, smart speaker, TV, etc.) at different locations (e.g., home, office, etc.).
  • the use that is associated with each of the multiple wireless devices may also be associated with multiple identities.
  • Call forwarding in existing 5G networks are not context aware such that an incoming call is not able to be forwarded to the user at the appropriate one of the multiple wireless devices at the appropriate time at the appropriate place, where appropriate device, time and place may be determined based on mobility information, for example.
  • existing business verticals do not have the capabilities to
  • Use case A Call forwarding based on wireless device mobility pattern
  • the car is observed to be parked (stationary) at a select parking location (office parking) as per the car’s weekdays mobility pattern during 8:00 AM to 5:00 PM (office timing).
  • Such mobility patterns can be studied using historical wireless device mobility patterns and communication patterns that are accessible to the network and/or network node to predict a time duration that the car may remain stationary as per select parking locations and hence can be used for intelligent call forwarding decisions on multiple wireless devices present between office and home.
  • incoming calls to the car can be recommended to be forwarded to a work phone, whereas the car parked at a home location during night hours, incoming calls can be recommended to be forwarded to the personal number during night time.
  • the locations can be classified based on the predicted time the devices may be in a stationary state, where different devices available at those locations may be used for forwarding an incoming call.
  • An example of the mobility of the car is illustrated in Table 1 where additional wireless device and identifications correspond to specific instances of predicated location and mobility.
  • Use Case B Call forwarding based on EV battery charging pattern
  • battery charging pattern time duration of charging, speed of charging, starting battery level
  • time duration of charging As per electric vehicle (car/wireless device) battery charging pattern (time duration of charging, speed of charging, starting battery level), it may be observed by the network that, during charging, the car is either at a home garage or at a charging station, but when charging is occurring at the home garage, the duration of the charging at the home garage extends a few hours. This may be due to voltage/load differences between commercial charging station and home (non-commercial) charging station. In other words, commercial charging locations may allow for quick charging, while non-commercial charging locations (e.g., home charging station) may require long hours for charging, which usually occurs overnight during non- working hours.
  • the network operator observing historical battery charging pattern can classify and predict whether a car is in a commercial charging location vs non-commercial charging location.
  • the system can recommend an incoming call to the car to be forwarded to another wireless device (i.e., smartphone), if the charging car is predicted to be at home or at a friend’s home (non-commercial charging location) for next few hours.
  • Table 2 illustrates additional wireless device and identifications that correspond to specific instances of predicated location and mobility.
  • Use case C Call forwarding if car/wireless device is predicted in a diagnostic mode
  • “connected car” corresponds to a group of heterogeneous devices, each relating to different functionalities, and a device health check of one or more of these devices is a common use case in networked society where a user can choose to trigger quick health check/scan of the car/wireless device; however, a full scan occurs at specialized car workshops over the span of several hours.
  • a remote health check over the network may generate health check traffic.
  • the connected car may be predicted to be in a type of diagnostic mode for automated remote health check as per health check communication traffic trends in the network. Based on past trends of such health check traffic, mobility pattern during such traffic generation, network operators may categorize car diagnostic modes, and a duration that the car may be in a diagnostic mode. That is, if the connected car is predicted to be in‘full’ diagnostic mode, the network operator can recommend that an incoming call to car/wireless device 4 be forwarded to another wireless device (e.g., smartphone) for some predicted time as indicated by algorithms as soon as car is predicted in a full scan (full diagnostic mode). Table 3 illustrates additional wireless device and identifications that correspond to specific instances of predicated diagnostic, time and days for a remote health check.
  • another wireless device e.g., smartphone
  • Use case D If an electric vehicle’s, i.e., type of wireless device, rechargeable battery rate of discharging is fast, another wireless device may be recommended for forwarding specific incoming callers to the electric vehicle where the callers are predicted to be long duration callers as per their historical communication pattern with user.
  • Table 4 illustrates predicted rate of discharging and an incoming caller type for the electric vehicle that correspond to various additional wireless devices and identifications.
  • Use case E Call forwarding on basis of Outliner Events for the time the wireless device is present in unsafe predicted locations if the wireless device is stationary in such locations beyond a configured threshold.
  • a self-driving logistic vehicle 8 i.e., type of wireless device, is moving
  • the self-driving logistic vehicle 8 passes through a recently predicted unsafe locality (a location is predicted to be unsafe by the network operator based on, for example, crime reporting rate (location based communication pattern of different wireless devices to 911) is very high recently). If 10 the self-driving logistic vehicle 8 is observed to be stationary at unsafe locations
  • this outliner event breaking from the pattern may trigger recommending forwarding of an incoming call from Administrator (business partner) to the vehicle 8 to another phone (driver number) till the time the self-driving logistic vehicle 8 restarts mobility again 15 and passes through unsafe location.
  • Administrator business partner
  • driver number another phone
  • the disclosure provides for dynamic initial filter criteria (IFC) in internet protocol multimedia subsystem (IMS) that enables, on a per session basis, the linking of a dynamic application server (AS) node that can affect the communication session, i.e., call, such as by changing the call display, introducing some context that can help call forwarding, etc., for example.
  • IFC internet protocol multimedia subsystem
  • AS application server
  • an AS node i.e., dynamic AS node
  • the dynamic AS node may be unidentified (i.e., not identified) in the wireless device’s/user’s predefined subscriber profile or not part of the wireless device’s/user’s predefined subscriber profile such that identifying and linking of the dynamic AS node is performed dynamically, i.e., dynamic linking, and not in a predefined manner using predefined AS nodes identified in the subscriber profile. This is in contrast to existing systems that can only link AS nodes that are identified in the predefined subscriber profile or predefined IMS subscription.
  • the system dynamically links the dynamic AS node to the session that may be identified by the wireless device at session initiation in the session initiation protocol (SIP) INVITE, i.e., SIP signaling, where the system may treat the identified AS node as if the identified AS node (i.e., dynamic AS node) was provisioned in the wireless device’s predefined IMS subscription as an originating AS node with an IFC trigger at session initiation (SIP INVITE).
  • This dynamically linked AS node i.e., dynamic AS node, may be the last AS node to link to the communication session after one or more other AS nodes that are in the wireless device’s predefined IMS subscription are linked to the communication session.
  • the wireless device may be provisioned with the dynamic AS node, i.e., vertical industry AS node, such that the wireless device identifies the dynamic AS node in the session SIP INVITE request initiated by the wireless device.
  • the dynamic AS node knows the business model to be implemented and can make the determination of how to impact the specific session INVITE request.
  • the dynamic AS node may modify one or more of the characteristics that can impact the session where the one or more characteristics include one or more of:
  • OLI originating line information
  • relational terms such as“first” and“second,”“top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms“a”,“an” and“the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term,“in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • the term“coupled,”“connected,” and the like may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • the node can be any kind of node that communicates directly and/or indirectly with an application server.
  • the node may be any of a base station (BS), node in the core network (i.e., core network node), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi- standard radio (MSR) radio node such as MSR BS, IMS node, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.),
  • MME mobile management entity
  • SON
  • wireless device or a user equipment (UE) are used interchangeably.
  • the WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD).
  • the WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), vehicle or device with wireless device capabilities such as a self-driving vehicle or drone, low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc.
  • D2D device to device
  • M2M machine to machine communication
  • vehicle or device with wireless device capabilities such as a self-driving vehicle or drone, low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by a wireless device or a node may be distributed over a plurality of wireless devices and/or nodes.
  • the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • FIG. 4 is a block diagram of an example system 15 for dynamic linking of an application server node for modifying at least one characteristic of a communication session in accordance with the principles of the disclosure.
  • System 15 includes one or more wireless devices 16 (WD 16), one or more nodes 18 and one or more application server nodes 20.
  • the WD 16 may have hardware 22 that may include a radio interface 24 configured to set up and maintain a wireless connection 26 with one or more nodes 18, application server nodes 20 and/or networks.
  • the radio interface 24 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the hardware 22 of the WD 16 further includes processing circuitry 28.
  • the processing circuitry 28 may include a processor 30 and memory 32.
  • the processing circuitry 28 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 30 may be configured to access (e.g., write to and/or read from) memory 32, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 32 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the WD 16 may further comprise software 34, which is stored in, for example, memory 32 at the WD 16, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 16.
  • the software 34 may be executable by the processing circuitry 28.
  • the software 34 may include a client application 36.
  • the client application 36 may be operable to provide a service to a human or non-human user via the WD 16 such as with the support of the node 18 and/or application server node 20.
  • the client application 36 may interact with the user to generate the user data that it provides.
  • the processing circuitry 28 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 16.
  • the processor 30 corresponds to one or more processors 30 for performing WD 16 functions described herein.
  • the WD 16 includes memory 32 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 34 and/or the client application 36 may include instructions that, when executed by the processor 30 and/or processing circuitry 28, causes the processor 30 and/or processing circuitry 28 to perform the processes described herein with respect to WD 16.
  • the processing circuitry 28 of the wireless device 16 may include a session unit 38 configured to initiate a session such as an IMS session as described herein.
  • the processing circuitry 28 may also include context unit 40 configured to perform at least function based on context aware information, as described herein.
  • wireless device 16 includes display 5 for displaying information such as Caller ID information, for example.
  • System 15 further includes a node 18 that includes hardware 42 enabling it to communicate with application server node 20 and with the WD 16.
  • the hardware 42 may include a communication interface 44 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 15, and may include a radio interface 46 for setting up and maintaining at least a wireless connection 26 with a WD 16.
  • the radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 44 may be configured to facilitate a connection 48 with application server node 20.
  • the connection 48 may be direct or it may pass through one or more networks such as an access and/or core network and/or IMS network.
  • node 18 may be a node implementing an S-CSCF in IMS, a GW in a core network or a base station in an access network. Thus, in some embodiments, node 18 may not directly communicate with a WD 16.
  • the hardware 42 further includes processing circuitry 50.
  • the processing circuitry 50 may include a processor 52 and a memory 54.
  • the processing circuitry 50 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 52 may be configured to access (e.g., write to and/or read from) the memory 54, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only
  • the memory 54 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only
  • the node 18 further has software 56 stored internally in, for example, memory 54, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the node 18 via an external connection.
  • the software 56 may be executable by the processing circuitry 50.
  • the processing circuitry 50 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by node 18.
  • Processor 52 corresponds to one or more processors 52 for performing node 18 functions described herein.
  • the memory 54 is configured to store data, programmatic software code and/or other information described herein.
  • the software 56 may include instructions that, when executed by the processor 52 and/or processing circuitry 50, causes the processor 52 and/or processing circuitry 50 to perform the processes described herein with respect to node 18.
  • processing circuitry 50 of the node 18 may include linking unit 58 that is configured to dynamic link a dynamic application server node 20 for modifying at least one characteristic of a communication session, as described herein.
  • System 15 includes one or more application server (AS) nodes 20 that may correspond to dynamic AS node 20, etc., as described herein.
  • AS node 20 includes hardware (HW) 60 including a communication interface 62 configured to set up and maintain a wired or wireless connection with an interface of a different
  • the AS node 20 further includes processing circuitry 64, which may have storage and/or processing capabilities.
  • the processing circuitry 64 may include a processor 66 and memory 68.
  • the processing circuitry 64 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 66 may be configured to access (e.g., write to and/or read from) memory 68, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 68 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 64 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., AS node 20.
  • Processor 66 corresponds to one or more processors 66 for performing AS node 20 functions described herein.
  • the AS node 20 includes memory 68 that is configured to store data, programmatic software code and/or other information described herein.
  • the software may include instructions that, when executed by the processor 66 and/or processing circuitry 64, causes the processor 66 and/or processing circuitry 64 to perform the processes described herein with respect to AS node 20.
  • the software 70 may be executable by the processing circuitry 64.
  • the processing circuitry 64 of the AS node 20 may include a modification unit 72 configured to modify at least one characteristic of a communication session, as described herein.
  • proxy AS node 20 may include similar hardware and software for performing proxy functions described herein but may not include modification unit 72 as proxy AS node may not perform the modifications described herein.
  • FIG. 4 shows various“units” such as session unit 38, linking unit 58, etc. as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 5 is a flowchart of an exemplary process in a wireless device 16 in accordance with some embodiments of the present disclosure.
  • One or more Blocks and/or functions performed by wireless device 16 may be performed by one or more elements of wireless device 16 such as by session unit 38 in processing circuitry 28, processor 30, radio interface 24, etc.
  • wireless device 16 such as via one or more of processing circuitry 28, processor 30, session unit 38 and radio interface 24 is configured to participate (Block S100) in the communication session where the session is linked with a dynamic application server node 20 that is unidentified (i.e., not identified) by the predefined subscriber profile, and where the dynamic application server node 20 is linked to the session based at least in part on a session context of the session.
  • the dynamic application server node 20 is configured to modify at least one characteristic of the session.
  • the at least one characteristic includes at least one of a call display and call forwarding to a different target device, i.e., target wireless device 22, than an original target wireless device 22.
  • the processing circuitry 64 is configured to, during initiation of the session, determine a session context of the session.
  • the processing circuitry 28 is further configured to cause transmission of a session initiation protocol, SIP, invite to initiate the session where the SIP invite identifying the dynamic application server node 20 to link to the communication session.
  • SIP session initiation protocol
  • the SIP invite identifies the dynamic application server node 20 by including a fully qualified domain name of the dynamic application server node 20 in the SIP invite.
  • the linking of the dynamic application server node 20 is on a per session basis.
  • the dynamic application server node 20 is linked to the session via a proxy application server node 20.
  • the session context corresponds to an inclusion of an application server Fully Qualified Domain Name, FQDN, in session initiation protocol INVITE signaling.
  • FIG. 6 is a flowchart of another exemplary process in a wireless device 16 such as a target wireless device in accordance with some embodiments of the present disclosure.
  • One or more Blocks and/or functions performed by wireless device 16 may be performed by one or more elements of wireless device 16 such as by context unit 40 in processing circuitry 28, processor 30, radio interface 24, etc.
  • wireless device 16 such as via one or more of processing circuitry 28, processor 30, context unit 40 and radio interface 24 is configured to receive (Block S102) context aware information.
  • wireless device 16 such as via one or more of processing circuitry 28, processor 30, context unit 40 and radio interface 24 is configured to execute (Block S104) a script based on the context aware information. Therefore, the target or called wireless device 16 is able to take some action depending on some context specific information related to the session that was inserted by dynamic AS node 20.
  • FIG. 7 is a flowchart of an exemplary process in a node 18 according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions performed by node 18 may be performed by one or more elements of node 18 such as by linking unit 58 in processing circuitry 50, processor 52, etc.
  • node 18 such as via one or more of processing circuitry 50, processor 52 and linking unit 58 is configured to receive (Block S106) signaling to initiate a session, as described herein.
  • wireless device 16 such as via one or more of processing circuitry 50, processor 52 and linking unit 58 is configured to link (Block S108) a dynamic application server node with the session where the dynamic application server node 20 is unidentified by the predefined subscriber profile and is linked based at least in part on a session context of the session.
  • the session initiation signaling identifies the dynamic application server node 20 by a fully qualified domain name of the dynamic application server node 20.
  • the processing circuitry 50 is further configured to: determine the session context of the session, determine the dynamic application server node 20 to link to the session based at least in part on the session context of the session, and determine a fully qualified domain name of the dynamic application server node 20 for linking to the session.
  • the session context corresponds to an inclusion of an application server Fully Qualified Domain Name, FQDN, in session initiation protocol INVITE signaling.
  • the linking of the dynamic application server node 20 to the session includes temporarily modifying the predefined subscriber profile for the session to link the dynamic application server node 20.
  • the node 18 corresponds to a serving call session control function, S-CSCF, node.
  • the dynamic application server node 20 is configured to modify at least one characteristics of the session.
  • the at least one characteristic includes at least one of a call display and call forwarding to a different target device than an original target device.
  • the linking of the dynamic application server node 20 is on a per session basis.
  • the dynamic application server node 20 is linked to the session via a proxy application server node 20, implemented on a node having similar structure as node 20.
  • the session initiation signaling corresponds to a session initiation protocol, SIP, invite message for initiating an internet protocol multimedia subsystem, IMS, session.
  • FIG. 8 is a flowchart of an exemplary process in an application server node 20 according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions performed by application server node 20 may be performed by one or more elements of application server node 20 such as by modification unit 72 in processing circuitry 64, processor 66, etc.
  • application server node 20 such as via one or more of processing circuitry 64, modification unit 72 and processor 66 is configured to receive (Block S 110) a SIP invite.
  • application server node 20 such as via one or more of processing circuitry 64, modification unit 72 and processor 66 is configured to update (Block S 112) the SIP invite to change at least one characteristic associated with the communication session.
  • FIGS 9a- 9b are signaling diagrams of an example process for linking a dynamic application server (AS) node 20b to a communication session in accordance with one or more embodiments of the disclosure.
  • the signaling diagram includes wireless device 16a, Proxy-Call Session Control Function (P-CSCF) node 18b, Serving Call Session Control Function (S-CSCF) 18a, MMTEL AS node 20c, proxy AS node 20a, dynamic AS node 20b and wireless device 16b.
  • P-CSCF Proxy-Call Session Control Function
  • S-CSCF Serving Call Session Control Function
  • MMTEL AS node 20c proxy AS node 20a
  • proxy AS node 20a proxy AS node 20a
  • dynamic AS node 20b dynamic AS node 20b
  • wireless device 16b wireless device 16b.
  • HSS home subscriber server
  • the dynamic AS node 20b i.e., AS1 is a vertical industry related AS in this example for illustration purposes, and links in as an originating IFC AS triggered at SIP INVITE following the multimedia telephony (MMTEL) AS node 20.
  • AS1 a vertical industry related AS in this example for illustration purposes, and links in as an originating IFC AS triggered at SIP INVITE following the multimedia telephony (MMTEL) AS node 20.
  • the proxy AS node 20a provides interworking with vertical industry related AS node 20 in a secure fashion.
  • the proxy AS node 20a may need to be able to query Domain Name System (DNS) related to vertical industry related AS nodes 20 to fetch the IP address of the dynamic AS node(s) to be linked.
  • DNS Domain Name System
  • Configuration may be needed in the proxy AS node 20a for this purpose but since the vertical industry may be considered a subscriber for the feature and for the IMS operator, such a configuration may not be an issue with modification of existing systems.
  • the wireless device 16a via processing circuitry 28, performs normal, i.e., known, IMS registration.
  • the node 18a i.e., S-CSCF
  • receives the wireless device IMS subscription profile i.e., predefined subscription profile.
  • the disclosure adds functionality to the existing or normal IMS registration by providing a new subscription feature referred to as dynamic IFC subscription.
  • the dynamic IFC subscription feature allows the wireless device 16a to have the dynamic AS node 20b included in its SIP INVITE (i.e., modified SIP INVITE) linked in as an originator IFC triggered AS node 20b after the MMTEL AS node 20c. This dynamic IFC subscription feature for node 18a is not provided in existing systems.
  • the SIP header (or any other parameters in an existing SIP header) included in the SIP INVITE conveying the AS IP address or Fully Qualified Domain Name (FQDN) may need to be known to the node 18a, i.e., S-CSCF.
  • the wireless device 16a via processing circuitry 28 and/or radio interface 24, initiates an IMS session and includes in the SIP INVITE the FQDN AS1 address of the dynamic AS node 20b to be linked by the node 18a in after the MMTEL AS node 20c.
  • the dynamic AS node 20b is not identified in the predefined subscriber profile associated with wireless device 16a.
  • the node 18a via processing circuitry 50, communication interface 44 and/or linking unit 58, receives signaling to initiate the session and links a dynamic AS node 20b with the session where the dynamic AS node 20b is unidentified by the predefined subscriber profile and is linked based at least in part on a session context of the session.
  • the node 18a via processing circuitry 50, communication interface 44 and/or linking unit 58, updates the wireless device subscription to allow wireless device 16a to link it to the dynamic AS node 20b, i.e., AS1, in the call chain as an originating IFC trigger for this session.
  • the node 18a forwards the SIP INVITE to the MMTEL AS node 20c, Block SI 18.
  • MTTEL AS node 20c via processing circuitry 64 and/or communication interface 62, returns the SIP INVITE to the node 18a as per existing IMS routing procedure.
  • the node 18a may link in a proxy AS node 20a for that purpose.
  • the Proxy AS node 20a may be owned by the IMS provider and enables routing of the SIP INVITE to the third party dynamic AS1 node 20b.
  • the dynamic AS node 20b via processing circuitry 64 and/or modification unit 72, updates the SIP invite to change at least one characteristic associated with the communication session, i.e., performs one or more changes to the SIP session, i.e., modifies/changes one or more characteristics of the SIP session, as shown in the call flow.
  • wireless device 16b in Block S104, via processing circuitry 28 and/or context unit 40, may execute a script based on context aware information inserted by dynamic AS node 20b.
  • wireless device 16b upon receipt of a SIP INVITE, wireless device 16b may be able to perform one or more actions depending on some context specific information related to the session that may be inserted by dynamic AS node 20b and that is understood by wireless device 16b. For example, one or more actions may include selective call forwarding or some other action that can span the IMS system or some other system’s outside IMS.
  • disclosure describes an example in which the dynamic linkage of the vertical industry related AS node 20b is triggered by the wireless 16a inclusion, in the SIP INVITE, of the AS FQDN.
  • the disclosure contemplates one or more other methods for triggering linkage of the dynamic AS node 20b.
  • the proxy AS node 20a may be configured with the Mobile Station International Subscriber Directory Number (MS ISDN) number series for wireless devices 16 and the related one or more dynamic AS node 20b that can be dynamically linked when these wireless devices 16 initiate IMS sessions, or the proxy AS node 20a may be configured with a wild carded SIP Uniform Resource Identifier (URIs) for originating wireless devices 16 that can also be configured with a vertical industry related AS, i.e., dynamic AS node 20b, to be dynamically linked for any wireless device 16 belonging to the wild carded SIP URI.
  • MS ISDN Mobile Station International Subscriber Directory Number
  • URIs Uniform Resource Identifier
  • SIP INVITE there may also be some other SIP headers in the SIP INVITE that can be configured in the Proxy AS node 20a, where filters can be set for matching similar to how IFC triggering works in S-CSCF.
  • Other configurations for linking dynamic AS node 20b are contemplated in accordance with the teachings of the disclosure.
  • FIGS. 10-14 illustrate various examples related to the examples of FIG. 3 except that at least one or more characteristics of the session have been modified based at least in part on session context of the session.
  • the calling party e.g., taxi 6, vehicle 14, bus 2, train 12, drone 10, etc.
  • the wireless device 16 that is initiating a call to another wireless device such as to wireless device 4, where taxi, vehicle 14, etc. are performing wireless device 16 functionality described herein.
  • a self driving taxi 6 i.e., a self-driving vehicle 14 during work hours
  • the session context can be considered, as described herein, to influence Caller ID in call setup to adapt to the rental vehicle business context.
  • vehicle identification number as per its license (calling name presentation), vehicle business category (as per business, network slice alias, calling business presentation), vehicle type (M2M device type, calling device presentation), etc.
  • a self-driving vehicle 14 may call wireless device 4 where the call is made during nonworking hours where the session context of the session is considered, as described herein, to adapt the Caller ID to reflect the non-working status (i.e.,“private”) of otherwise working vehicles 14 as illustrated in FIG. 11.
  • vehicle identification number as per its license (calling name presentation), vehicle access modification category (network slice alias, calling business presentation), vehicle type (M2M device type, calling vehicle presentation).
  • vehicle 14 may be used by different employers associated with different businesses across verticals for different hours as illustrated in FIG. 11, i.e., work profiles, such that these various profiles can be considered for adapting one or more characteristics of the session such as call forwarding to a different target device than an original target device.
  • a self-driving bus 2 calls wireless device 16 that is associated with a passenger of the self-driving bus 2.
  • the self-driving bus 2 is making the call to wireless device 4 to inform the passenger that the bus 2 is about to depart where the session context of the session is considered, as described herein, to adapt the Caller ID such as per a specific route (School route, Factory route) context based on business as illustrated in FIG. 12. For example, one or more of the following information that is based on the session context may be displayed: vehicle
  • a self-driving train 12 is calling wireless device 4 that is associated with one of its passengers to report to train 12 as it about to depart the station where the session context of the session is considered, as described herein, to adapt one or more characteristics of the communication session such as the Caller ID to personalize the call displays using the reservation details context as illustrated in FIG. 13.
  • train name For example, one or more of the following information that is based on the session context may be displayed: train name, cabin number and/or passenger seat identification number as per reservation (train subscription profile for a journey on a day, calling name presentation), train cabin business category (1AC, 2AC, 3 AC, sleeper; network slice alias, calling business presentation), connected train (calling device presentation), etc.
  • a drone (UAV) 10 is calling wireless device 4 associated with a customer in order for the customer to accept delivering of the e-commerce product/pizza as the drone 10 reaches the destination where the session context of the session is considered, as described herein, to adapt one or more characteristics of the communication session such as the Caller ID based on the delivery context (e.g., 15 minute delivery (“15MINS”), 30 minute delivery) from the time pizza order is placed online until the time when the call is received from drone 10 after reaching the customer location as illustrated in FIG. 14.
  • the delivery context e.g., 15 minute delivery (“15MINS”), 30 minute delivery
  • M2M device type calling device representation
  • delivery category as per food business (15 min delivery, 30 min delivery; network slice alias; calling business presentation
  • drone identification number as per its license (subscription profile, calling name representation), etc.
  • the disclosure provides for dynamic IFC in IMS that enables, on a per session basis, the linkage of a new AS node 20, i.e., one or more dynamic AS nodes 20b, that can affect one or more characteristics of the session, i.e., the actual call (e.g. changing the call display, introducing some context that can help call forwarding, etc.).
  • the dynamic linking of a one or more dynamic AS nodes 20b as described herein provides one or more of the following advantages:
  • the dynamic linking described herein provides for context aware calls that can empower business verticals to control the call experience (call displays, call forwarding) based on context towards its end-customers.
  • the machine and human communication service experience in 5G networks can be better controlled by businesses in different verticals using the dynamic linking for its wireless devices 16 (e.g., self-driving device) with call capabilities involved in call.
  • 5G Operators With an increase in wireless devices 16 with 5G operator supported communication services, the dynamic linking described herein can be part of different business verticals supporting different use cases where such network capabilities may open new revenue source(s) for 5G operators.
  • End-Customer The dynamic linking described herein may help improve end user call experience with machines in different use cases.
  • the concepts described herein may be embodied as a method, data processing system, and/or computer program product. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or“module.” Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un dispositif sans fil, un nœud et des procédés. Dans un ou plusieurs modes de réalisation, l'invention concerne un dispositif sans fil configuré avec un profil d'abonné prédéfini qui identifie un nœud de serveur d'application pour se connecter à une session de communication. Le dispositif sans fil comprend des circuits de traitement conçus pour participer à la session lorsque la session est liée à un nœud de serveur d'application dynamique qui n'est pas identifié par le profil d'abonné prédéfini et lorsque le nœud de serveur d'application dynamique est lié à la session sur la base, au moins en partie, d'un contexte de session de la session.
PCT/IB2019/053611 2019-05-02 2019-05-02 Critères de filtrage initial dynamique (ifc) dans un sous-système multimédia de protocole internet (ims) dans des réseaux de 5e génération WO2020222036A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2019/053611 WO2020222036A1 (fr) 2019-05-02 2019-05-02 Critères de filtrage initial dynamique (ifc) dans un sous-système multimédia de protocole internet (ims) dans des réseaux de 5e génération

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2019/053611 WO2020222036A1 (fr) 2019-05-02 2019-05-02 Critères de filtrage initial dynamique (ifc) dans un sous-système multimédia de protocole internet (ims) dans des réseaux de 5e génération

Publications (1)

Publication Number Publication Date
WO2020222036A1 true WO2020222036A1 (fr) 2020-11-05

Family

ID=66951987

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2019/053611 WO2020222036A1 (fr) 2019-05-02 2019-05-02 Critères de filtrage initial dynamique (ifc) dans un sous-système multimédia de protocole internet (ims) dans des réseaux de 5e génération

Country Status (1)

Country Link
WO (1) WO2020222036A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007009498A1 (fr) * 2005-07-19 2007-01-25 Telefonaktiebolaget Lm Ericsson (Publ) Procede et appareil de distribution d'adresses de serveur dans un ims
US8170534B2 (en) * 2007-04-17 2012-05-01 Aylus Networks, Inc. Systems and methods for user sessions with dynamic service selection
US9148453B1 (en) * 2011-03-14 2015-09-29 Sprint Communications Company L.P. Dynamic determination of initial filter criteria
EP2928155A2 (fr) * 2006-03-21 2015-10-07 Samsung Electronics Co., Ltd Procédé et système de traitement d'un message de commande dans un système de communication mobile basé sur un protocole internet prenant en charge un service multimédia

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007009498A1 (fr) * 2005-07-19 2007-01-25 Telefonaktiebolaget Lm Ericsson (Publ) Procede et appareil de distribution d'adresses de serveur dans un ims
EP2928155A2 (fr) * 2006-03-21 2015-10-07 Samsung Electronics Co., Ltd Procédé et système de traitement d'un message de commande dans un système de communication mobile basé sur un protocole internet prenant en charge un service multimédia
US8170534B2 (en) * 2007-04-17 2012-05-01 Aylus Networks, Inc. Systems and methods for user sessions with dynamic service selection
US9148453B1 (en) * 2011-03-14 2015-09-29 Sprint Communications Company L.P. Dynamic determination of initial filter criteria

Similar Documents

Publication Publication Date Title
US11470657B2 (en) Method, user equipment, and network node for performing PDU session establishment procedure for LADN
US11997592B2 (en) PLMN selection for mission critical devices
US20230080830A1 (en) EXTENSION OF Npcf_EventExposure WITH USAGE MONITORING EVENT
US10034237B2 (en) System and method to facilitate hotspot onboarding for user equipment in a network environment
CA3061464A1 (fr) Procede d'execution d'une procedure relative a l'enregistrement d'une fonction de gestion d'acces et de mobilite (amf) par gestion de donnees unifiee (udm) dans un systeme de comm unication sans fil, et dispositif associe
WO2019073977A1 (fr) Configuration et mise à jour d'ue avec une politique de sélection de tranche de réseau
US9839061B2 (en) Establishing and configuring dynamic subscriptions
US20210160691A1 (en) Systems and method for secure updates of configuration parameters provisioned in user equipment
US10135883B1 (en) Method and system for over-the-top voice for internet of things devices
US20230045195A1 (en) First Node, Second Node and Methods Performed Thereby for Handling Identification of a Communications Network
US10917867B2 (en) Optimized handling of a UE in MICO mode with entire PLMN as registration area
CN112005580B (zh) 边缘服务连续性
US11871339B2 (en) Filters for bulk subscriptions
WO2023120045A1 (fr) Procédé d'appareil de communication, procédé d'équipement utilisateur (ue), appareil de communication, ue, procédé pour un premier appareil de communication, procédé pour terminal de communication et procédé pour un premier appareil de communication
US20240187972A1 (en) NF DISCOVERY BETWEEN DIFFERENT NETWORKS SUCH AS DIFFERENT SNPNs
WO2022270259A1 (fr) Procédé d'appareil de fonction de gestion de session (smf), procédé d'appareil de fonction de commande d'admission de tranche de réseau (nsacf), procédé d'appareil de fonction de gestion de mobilité et d'accès (amf), procédé d'appareil associé à smf, appareil smf, appareil nsacf, appareil amf et appareil associé à smf
WO2020222036A1 (fr) Critères de filtrage initial dynamique (ifc) dans un sous-système multimédia de protocole internet (ims) dans des réseaux de 5e génération
US20240114414A1 (en) Method and apparatus for providing network switching service in 5g communication system
WO2024117117A1 (fr) Procédé exécuté par un premier nœud de réseau central, procédé d'équipement utilisateur, premier nœud de réseau central et équipement utilisateur
US20240205863A1 (en) Apparatuses, methods, and computer program products for fifth-generation system multiple registration with evolved packet system network interworking
US20240260112A1 (en) Method performed by radio terminal and radio terminal
WO2023286779A1 (fr) Procédé exécuté par un terminal radio, et terminal radio
US20240259932A1 (en) Method for network node and network node
US10433154B2 (en) Attribute indicating a home component of a subscriber
WO2023170652A1 (fr) Gestion de service dans des réseaux sans fil

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: 19731788

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19731788

Country of ref document: EP

Kind code of ref document: A1