Service-based Internet Protocol Multimedia Subsystem (IMS) Architecture

Abstract

A system and method for extending a service-based architecture to an Internet Protocol (IP) Multimedia Subsystem (IMS) is disclosed. In one exemplary aspect, a wireless communication method includes sending a registration request by a network node in the IMS to a Network Capability Repository Function (NRF) via a first service-based network interface. The registration request includes capability information of the network node indicating support for one or more services.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application is an international patent application claiming the benefit of U.S. Patent Application No. 63 / 324,547, filed March 28, 2022, entitled "SERVICE-BASED INTERNET PROTOCOL MULTIMEDIA SUBSYSTEM (IMS) ARCHITECTURE," which is incorporated herein by reference in its entirety. [Background technology]

[0002] Mobile communications technology is moving the world toward an increasingly connected and networked society. The fifth-generation (5G) New Radio (NR) architecture is based on service-based architecture (SBA), an architectural approach that enables finer separation of 5G network functions. SBA allows individual services to be updated independently with minimal impact on other services, thereby providing vendor independence, faster deployment times, and improved operational efficiency. [Brief explanation of the drawings]

[0003] [Figure 1] 1 illustrates an exemplary 5G reference architecture in which service-based interfaces are used within the control plane. [Figure 2] 1 illustrates an exemplary Internet Protocol (IP) Multimedia Subsystem (IMS) architecture. [Figure 3] 1 illustrates an exemplary architecture for IMS application function (AF) discovery via a Domain Name Server (DNS). [Figure 4] FIG. 1 illustrates an example architecture of a service-based architecture IMS in accordance with one or more embodiments of the present technology. [Figure 5] FIG. 1 illustrates an example sequence flow of an IMS node registration procedure in accordance with one or more embodiments of the present technology. [Figure 6] 1 illustrates an exemplary sequence flow of a Network Function Repository Function (NRF) subscription procedure in accordance with one or more embodiments of the present technology. [Figure 7] FIG. 1 illustrates an example sequence flow for an IMS node discovery and selection procedure in accordance with one or more embodiments of the present technology. [Figure 8A] FIG. 1 is a flowchart diagram of a method for wireless communication in accordance with one or more embodiments of the present technology. [Figure 8B] FIG. 10 is a flowchart diagram of another method for wireless communication in accordance with one or more embodiments of the present technology. [Figure 9] FIG. 10 is yet another flow chart diagram for wireless communication in accordance with one or more embodiments of the present technology. [Figure 10] FIG. 1 illustrates an example wireless communication network incorporating aspects of the disclosed technology. [Figure 11] FIG. 1 is a block diagram illustrating an example of a computer system capable of performing at least some of the operations described herein.

[0004] The technology described herein will become more apparent to those skilled in the art upon review of the detailed description in conjunction with the drawings. Embodiments or implementations illustrating aspects of the present invention are shown by way of example, and like reference numerals may refer to similar elements. While the drawings show various implementations for illustrative purposes, those skilled in the art will recognize that alternative embodiments may be employed without departing from the principles of the technology. Thus, while specific implementations are shown in the drawings, the technology is susceptible to various modifications. DETAILED DESCRIPTION OF THE INVENTION

[0005] Section headings are used in this document only to improve readability and do not limit the scope of the disclosed embodiments and technologies in each section to that section alone. The example of a fifth-generation (5G) wireless protocol is used to illustrate certain features. However, the applicability of the disclosed technologies is not limited to 5G wireless systems alone.

[0006] Systems, methods, and devices for extending a service-based architecture to Internet Protocol (IP) Multimedia Subsystem (IMS) are disclosed to enable discovery and selection of IMS nodes using uniform interfaces and mechanisms as non-IMS functions in 5G networks, thereby reducing complexity in signaling, monitoring, and deployment of network elements.

[0007] The 5G service-based architecture was introduced in Release 15 of the Third Generation Partnership Project (3GPP) standards. Figure 1 shows an example 5G reference architecture 100 in which service-based interfaces are used within the control plane. The Network Function Repository Function (NRF) is a key element of the service-based architecture. The NRF is a logical function used to support the functionality of Network Functions (NFs) and NF service discovery. The NRF provides a single record of available Network Functions (NFs) in a given Public Land Mobile Network (PLMN) along with NF capabilities indicating the services they support. The capabilities are then used when NF selection is performed.

[0008] In cellular networks, the Internet Protocol (IP) Multimedia Subsystem (IMS) is an architectural framework for delivering IP multimedia services. The IMS uses Internet Engineering Task Force (IETF) protocols, such as the Session Initiation Protocol (SIP), for signaling transmission. Figure 2 shows an exemplary IMS architecture 200. Several SIP server or proxy roles, collectively called Call Session Control Functions (CSCFs), are used to process SIP signaling packets in the IMS. The Proxy-CSCF (P-CSCF) is a SIP proxy that is the first point of contact for an IMS terminal. The Interrogating-CSCF (I-CSCF) is another SIP function located at the edge of the administrative domain, and its IP address is published in the Domain Name System (DNS) so that remote servers can find it and use it as a forwarding point for SIP packets. The Serving-CSCF (S-CSCF) is the central node in the signaling plane. Conventionally, the S-CSCF uses the Diameter Cx and Dx interfaces to the Home Subscriber Server (HSS) to download user profiles and upload user associations.

[0009] For backward compatibility with previous deployments of IMS and 5GC features, the 5G system architecture supports the N5 interface and the Rx interface between the Policy Control Function (PCF) and the P-CSCF to enable IMS services. In Release 16 of the 3GPP standard, IMS was extended to utilize several service-based interfaces (e.g., toward the P-CSCF, PCF, and / or HSS). Currently, the P-CSCF selection function can be used by the Session Management Function (SMF) to select a P-CSCF for a user equipment (UE) IMS protocol data unit (PDU) session. The SMF can discover the P-CSCF using the NRF. However, other IMS elements, such as the I / S-CSCF, Telephony Application Server (TAS), Rich Communication Services (RCS), Breakout Gateway Control Function (BGCF), and / or Interconnection Border Control Function (IBCF), utilize the IMS Domain Name Server (DNS) to resolve next-hop addresses.

[0010] FIG. 3 illustrates an example architecture 300 for IMS application function (AF) discovery via DNS. In this architecture, DNS provides discovery and domain selection through service-based load sharing. Specifically, an IMS management node monitors IMS nodes via Simple Network Management Protocol (SNMP) or Hypertext Transfer Protocol (HTTP) and excludes nodes from selection if they handle a large traffic load within the domain or are down for maintenance. IMS node discovery and selection can be preconfigured or utilize DNS to determine which nodes are appropriate for the services used by an IMS user. For example, to select an IMS media resource function (MRF) specialized in video codec adaptation, an IMS video application server (AS) must be configured with a list of fully qualified domain names (FQDNs) associated with a pool of MRFs capable of performing video codec adaptation.

[0011] The DNS-based discovery and selection process shown in FIG. 3 is not aligned with the 5G service-based architecture. Furthermore, point-to-point interfaces between IMS elements (e.g., IMS management node and AF) also introduce complexity and signaling overhead. This patent document discloses techniques that can be implemented in various embodiments to extend the service-based architecture to the IMS to enable IMS AF discovery and selection using uniform interfaces and mechanisms as non-IMS AFs. FIG. 4 illustrates an example architecture 400 of a service-based architecture IMS in accordance with one or more embodiments of the present technology. As shown in FIG. 4, an N-NRF can replace the functionality of an IMS DNS and / or an IMS management node for IMS node discovery, selection, and / or monitoring via a service-based interface. In some embodiments, the NRF can be adapted to support IMS node discovery and / or selection. The NRF can support IMS node registration and IMS node subscription to obtain node information (e.g., traffic load). In some embodiments, additional information, such as network function type and / or service capability extensions, can be included in the IMS node registration process. The NF discovery service can be adapted to support IMS application server discovery / selection (e.g., based on IMS node capabilities). In some embodiments, one or more new interfaces consistent with existing SBAs can be added to support subscription and node state notification (e.g., service load). Within the IMS, IMS nodes can be adapted to support a service-based architecture. IMS nodes can register with the NRF to offer capabilities to support various services and provide node information to the NRF.

[0012] FIG. 5 illustrates an example sequence flow 500 for an IMS node registration procedure in accordance with one or more embodiments of the present technology. Upon initialization, an IMS node performs an NF registration procedure with the NRF. As shown in FIG. 5, in operation 501, the IMS node sends a request message (e.g., an Nnrf_NF_Management_NF_REGISTRATION_Request message) to inform the NRF of its profile when the IMS node first becomes operational. The profile includes one or more services supported by the node. In some embodiments, the profile may include an alphanumeric sequence (e.g., a wildcard string) to indicate support for all services within a particular category. In addition to indicating capabilities, the IMS node may also include other types of parameters in the profile, such as its location, priority, etc. Other parameters that may be carried in the profile include, but are not limited to, an IP address, an IMS region, an international mobile subscriber identity (IMSI) range, the mobile country code (MCC) and / or mobile network code (MNC) of supported PLMN networks (MCC / MNC), and / or supported 5G slices. In operation 502, the NRF stores the IMS node's profile and marks it as available. In operation 503, the NRF confirms the IMS node registration via a response message (e.g., an Nnrf_NFManagement_NFRegistrationResponse message). In some embodiments, in a distributed MRF implementation where the MRF Controller (MRFC) and MRF Processor (MRFP) are distributed, the MRFC and / or MRFP may follow a registration process consistent with the flow shown in Figure 5. In some embodiments, if the pairing is known or pre-configured, only one of the MRFC or MRFP needs to register.

[0013] After successful registration, an IMS node can send updates to the NRF to communicate changes to its profile. Updates can be sent periodically or can be triggered by pre-configured / pre-defined events. Updates are used to communicate changes in the network's conditions or capabilities to better handle offered traffic to the IMS node. For example, the network can adapt and adjust the load of a selected IMS node when it detects that the node is overloaded or underloaded.

[0014] In some embodiments, the NRF can optionally subscribe to an IMS node for information about the node (e.g., the load status of the IMS node). FIG. 6 illustrates an example sequence flow 600 for an NRF subscription procedure in accordance with one or more embodiments of the present technology. In operation 601, the NRF sends a subscription request (e.g., an Nxxx_eventexposure subscription request) to the IMS node so that it can be notified of status changes (e.g., load changes) of the IMS node. In operation 602, the IMS node grants the NRF request. In operation 603, the IMS node sends a response message (e.g., an Nxxx_eventexposure subscription response) indicating that the request was successfully accepted. In operation 604, the IMS node notifies the subscribed NRF (e.g., using an Nxxx_eventexposure notification service) if there is a change in its status (e.g., traffic load). For example, the load status of the IMS node can include processor load, media channel, or data throughput. An IMS node can notify the NRF when it detects that its load exceeds one or more specific thresholds (e.g., 90%). The interface between the NRF and the IMS node for subscription / notification can be named according to the type of service the IMS node supports. For example, for an IMS Media Resource Function (MRF) node, a new interface, Nmrf, can be added to provide subscription and notification signaling.

[0015] When an IMS application server needs a corresponding IMS node to perform operations for a particular service, the IMS AS requests service discovery / selection by the NRF. FIG. 7 illustrates an example sequence flow 700 for an IMS node discovery and selection procedure in accordance with one or more embodiments of the present technology. At operation 701, an IMS NF (e.g., a CSCF, an AS, etc.) invokes IMS node discovery by sending a request (e.g., an Nnrf_NFDiscover_Request) to the NRF. The request may include information about one or more services supported by at least one IMS node. In some embodiments, the request may include a wildcard string indicating all services within a particular category. At operation 702, the NRF grants the discovery request in accordance with 5G SBA practices. At operation 703, the NRF determines one or more IMS nodes that match the service indicated by the request and its internal policies. The NRF then sends information about the one or more IMS nodes to the IMS NF via a response message (e.g., an Nnrf_NFDiscover_Request). In some embodiments, in a distributed MRF implementation where the MRFC and MRFP are distributed, the MRFC and / or MRFP may be discovered / selected consistent with the flow shown in FIG.

[0016] For example, the discovery request may include capabilities for a particular IMS service. In some embodiments, the NRF performs IMS node discovery, and the IMS AS performs IMS node selection. The NRF can respond with a list of IMS nodes that can satisfy the required service capabilities, along with other NRF parameters (e.g., by location, priority, load, etc.). The IMS AS can select an appropriate IMS node based on characteristics and / or properties of the IMS node, such as IP address, IMS region, non-public network identifier, PLMN identifier, roaming status, visited PLMN address(es), UE International Mobile Equipment Identity (IMEI), UE IMSI, UE Mobile Station International Subscriber Directory Number (MSISDN), HSS group ID, required identifier(s) of the network slice or slices, etc. In some embodiments, the NRF can perform both IMS node discovery and selection. The NRF can respond with a specific IMS node selected from the list of IMS nodes that satisfy the service requirements.

[0017] Depending on the implementation of the IMS AS, the AS can request each service individually or a specific set together (e.g., a TAS that supports voice services can request all voice services the first time it needs the services for a particular user, or it can request each voice service individually when it needs to provide a particular service for the user).

[0018] One category of IMS services is media services (e.g., media resource functions, MRFs). Examples of media services include, but are not limited to, at least one of audio announcements, audio conferencing, audio codec adaptation, video codec adaptation, video conferencing, etc. Other categories of IMS services include, but are not limited to, text messaging (including SMS interworking), Rich Communications Suite (RCS), end-to-end (or peer-to-peer) user data channels, IMS gaming services, IMS alternative / augmented reality, real-time text (RTT), and automatic language translation services.

[0019] 8A is a flowchart diagram of a process 800 for wireless communication in accordance with one or more embodiments of the present technology. The process 800 includes, at operation 810, sending a registration request by a network node in an Internet Protocol (IP) Multimedia Subsystem (IMS) to a Network Capability Repository Function (NRF) via a first service-based network interface. The registration request includes capability information of the network node indicating support for one or more services. In some embodiments, the method includes receiving, by the network node, a subscription request from the NRF via a second service-based network interface and notifying the NRF of information regarding the state of the network node via the second service-based network interface. In some embodiments, the information regarding the state of the network node includes load information of the network node (e.g., processor load, network state, etc.). In some embodiments, the registration request includes information indicating a network capability type of the network node (e.g., media service / media capability). In some embodiments, the first service-based network interface includes an Nnrf interface.

[0020] 8B is a flowchart diagram of a process 850 for wireless communication in accordance with one or more embodiments of the present technology. The process 850 includes, at operation 860, receiving, by a Network Capability Repository Function (NRF), a registration request from a network node in an Internet Protocol (IP) Multimedia Subsystem (IMS) via a first service-based network interface. The registration request includes capability information of the network node indicating support for one or more services. In some embodiments, the method includes sending, by the NRF, a join request to the network node via a second service-based network interface, and monitoring, by the NRF, a status of the network node in response to the join request. In some embodiments, the status of the network node includes load information of the network node. In some embodiments, the registration request includes information indicating a network capability type of the network node. In some embodiments, the first service-based network interface includes an Nnrf interface. In some embodiments, the method includes: an NRF receiving a service request for a specified service from an application server of an IMS; and the NRF determining, according to capability information of network nodes in the IMS, one or more network nodes that support the specified service in response to the service request.

[0021] 9 is a flowchart diagram of a process 900 for wireless communication in accordance with one or more embodiments of the present technology. Process 900 includes, at operation 910, sending a service request for a specified service by an application server, an Internet Protocol (IP) Multimedia Subsystem (IMS), to a Network Function Repository Function (NRF). Process 900 also includes, at operation 920, receiving one or more network nodes that support the specified service in response to the service request. In some embodiments, the method includes selecting, by the application server, a network node from one or more network nodes provided by the NRF.

[0022] For example, the network node comprises a media resource function (MRF). The capability information includes support for at least one of an audio announcement service, an audio conferencing service, an audio codec adaptation service, a video codec adaptation service, and a video conferencing service. The second service-based network interface can be named according to a service type (e.g., an Nmrf interface).

[0023] An example of a change that can be made to 3GPP Technical Specification (TS) 23.228 is shown in Table 1 below.

[0024] [Table 1]

[0025] Another example of changes that can be made to 3GPP TS23.502 (in bold and underlined text) is shown in Table 2 below.

[0026] [Table 2]

[0027] wireless communication system

[0028] FIG. 10 illustrates a wireless communication network 1000 ("network 1000") incorporating aspects of the disclosed technology. Network 1000 includes base stations 1002-1 through 1002-4 (which may be individually referred to as "base stations 1002" or collectively referred to as "base stations 1002"). A base station is a type of network access node (NAN), which may also be referred to as a cell site, a base transceiver station, or a wireless base station. Network 1000 may include any combination of NANs, including access points, wireless transceivers, gNodeBs (gNBs), NodeBs, eNodeBs (eNBs), Home NodeBs, or Home eNodeBs. In addition to being wireless wide area network (WWAN) base stations, NANs may be wireless local area network (WLAN) access points, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 access points.

[0029] The NAN of network 1000 formed by network 1000 also includes wireless devices 1004-1 through 1004-7 (individually referred to as “wireless devices 1004” or collectively “wireless devices 1004”) and core network 1006. Wireless devices 1004-1 through 1004-7 may correspond to or include network 1000 entities capable of communicating using various connectivity standards. For example, 5G communication channels may use millimeter wave (mmW) access frequencies above 28 GHz. In some implementations, wireless device 1004 may operably couple to base station 1002 over a Long Term Evolution / Long Term Evolution Advanced (LTE / LTE-A) communication channel, also referred to as a 4G communication channel.

[0030] The core network 1006 provides, manages, and controls security services, user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The base stations 1002 interface with the core network 1006 via a first set of backhaul links (e.g., an S1 interface) and may perform radio configuration and scheduling for communicating with the wireless devices 1004, or may operate under the control of a base station controller (not shown). In some examples, the base stations 1002 may communicate with each other directly or indirectly (e.g., via the core network 1006) via a second set of backhaul links 1010-1 through 1010-3 (e.g., an X1 interface), which may be wired or wireless communication links.

[0031] The base station 1002 can wirelessly communicate with wireless devices 1004 via one or more base station antennas. The cell sites can provide communication coverage for geographic coverage areas 1012-1 through 1012-4 (individually referred to as “coverage areas 1012” or collectively referred to as “coverage areas 1012”). The geographic coverage area 1012 of the base station 1002 can be divided into sectors that make up only a portion of the coverage area (not shown). The network 1000 can include different types of base stations (e.g., macro and / or small cell base stations). In some implementations, there can be overlapping geographic coverage areas 1012 for different service environments (e.g., Internet of Things (IoT), Mobile Broadband (MBB), Vehicle-to-Everything (V2X), Machine-to-Machine (M2M), Machine-to-Everything (M2X), Ultra-Reliable Low Latency Communications (URLLC), Machine-Type Communications (MTC), etc.).

[0032] The network 1000 may include a 5G network 1000 and / or an LTE / LTE-A or other network. In an LTE / LTE-A network, the term eNB is used to describe a base station 1002, and in a 5G new radio (NR) network, the term gNB is used to describe a base station 1002 that may include mmW communications. Thus, the network 1000 may form a heterogeneous network 1000 in which different types of base stations provide coverage for various geographic regions. For example, each base station 1002 may provide communication coverage for a macro cell, a small cell, and / or other types of cell. As used herein, the term “cell” can refer to a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector) of a carrier or base station, depending on the context.

[0033] A macrocell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow access by wireless devices having a service subscription with the service provider of the wireless network 1000. As previously indicated, a small cell is a low-power base station compared to a macrocell and may operate in the same or a different (e.g., licensed, unlicensed) frequency band as the macrocell. Examples of small cells include picocells, femtocells, and microcells. Generally, a picocell may cover a relatively small geographic area and may allow unrestricted access by wireless devices having a service subscription with the network 1000 provider. A femtocell may cover a relatively small geographic area (e.g., a home) and may provide limited access by wireless devices having an association with a femto unit (e.g., wireless devices in a closed subscriber group (CSG), wireless devices for users within a home). A base station may support one or more (e.g., two, three, four, etc.) cells (e.g., component carriers). All fixed transceivers described herein that can provide access to the network 1000 are NANs, including small cells.

[0034] A communication network corresponding to the various disclosed examples may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer then performs packet segmentation and reassembly for communications over logical channels. The Medium Access Control (MAC) layer may perform prioritized processing and multiplexing of logical channels onto transport channels. The MAC layer may also use Hybrid ARQ (HARQ) to provide retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer provides establishment, configuration, and maintenance of RRC connections between the wireless device 1004 and the base station 1002 or core network 1006 supporting radio bearers for user plane data. In the physical (PHY) layer, transport channels are mapped to physical channels.

[0035] Wireless devices may be integrated with or embedded in other devices. As shown, wireless devices 1004 are distributed throughout the system 1000, and each wireless device 1004 may be stationary or mobile. For example, the wireless devices may include handheld mobile devices 1004-1 and 1004-2 (e.g., smartphones, portable hotspots, tablets, etc.); laptops 1004-3; wearables 1004-4; drones 1004-5; vehicles with wireless connectivity 1004-6; head-mounted displays with wireless augmented reality / virtual reality (AR / VR) connectivity 1004-7; handheld game consoles; wireless routers, gateways, modems, and other fixed wireless access devices; wirelessly connected sensors that provide data to a remote server over a network; and IoT devices such as wirelessly connected smart home appliances.

[0036] The wireless devices (e.g., wireless devices 1004-1, 1004-2, 1004-3, 1004-4, 1004-5, 1004-6, and 1004-7) may be referred to as user equipment (UE), customer premises equipment (CPE), mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, handheld mobile device, remote device, mobile subscriber station, terminal equipment, access terminal, mobile terminal, wireless terminal, remote terminal, handset, mobile client, client, etc.

[0037] The wireless devices may communicate with various types of base stations and network 1000 equipment at the edge of the network 1000, including macro eNB / gNBs, small cell eNB / gNBs, relay base stations, etc. The wireless devices may also communicate with other wireless devices within or outside the same coverage area of ​​the base station via device-to-device (D2D) communication.

[0038] The communication links 1014-1 through 1014-9 (individually referred to as "communication links 1014" or collectively referred to as "communication links 1014") shown in network 1000 include uplink (UL) transmissions from wireless device 1004 to base station 1002 and / or downlink (DL) transmissions from base station 1002 to wireless device 1004. Downlink transmissions may also be referred to as forward link transmissions, and uplink transmissions may also be referred to as reverse link transmissions. Each communication link 1014 includes one or more carriers, each of which may be a signal composed of multiple subcarriers (e.g., waveform signals at different frequencies) modulated according to various radio technologies. Each modulated signal is transmitted on a different subcarrier and may carry control information (e.g., reference signals, control channels), overhead information, user data, etc. The communication links 1014 may transmit bidirectional communications using frequency division duplexing (FDD) (e.g., using paired spectrum resources) or time division duplexing (TDD) operation (e.g., using unpaired spectrum resources). In some implementations, the communication link 1014 includes an LTE and / or mmW communication link.

[0039] In some implementations of network 1000, base station 1002 and / or wireless device 1004 include multiple antennas for employing antenna diversity schemes to improve communication quality and reliability between base station 1002 and wireless device 1004. Additionally or alternatively, base station 1002 and / or wireless device 1004 may employ multiple-input, multiple-output (MIMO) techniques that may take advantage of multipath environments and transmit multiple spatial layers carrying the same or different coded data.

[0040] Computer Systems

[0041] 11 is a block diagram illustrating an example of a computer system 1100 capable of performing at least some operations described herein. As shown, computer system 1100 may include one or more processors 1102, a main memory 1106, a non-volatile memory 1110, a network interface device 1112, a video display device 1118, input / output devices 1120, a control device 1122 (e.g., a keyboard and pointing device), a drive unit 1124 including a storage medium 1126, and a signal generating device 1130 communicatively coupled to a bus 1116. Bus 1116 represents one or more physical buses and / or point-to-point connections connected by appropriate bridges, adapters, or controllers. For simplicity, various typical components (e.g., cache memory) have been omitted from FIG. 7. Instead, computer system 1100 is intended to represent a hardware device in which the components shown or described in connection with the illustrative example and any other components described herein may be implemented.

[0042] Computer system 1100 can take any suitable physical form. For example, computing system 1100 can share an architecture similar to that of a server computer, a personal computer (PC), a tablet computer, a mobile phone, a game console, a music player, a wearable electronic device, a network-connected (“smart”) device (e.g., a television or home assistant device), an AR / VR system (e.g., a head-mounted display), or any electronic device capable of executing a set of instructions that specify operations to be performed by computing system 1100. In some implementations, computer system 1100 can be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC), or a distributed system such as a mesh of computer systems, or can include one or more cloud components in one or more networks. Where appropriate, one or more computer systems 1100 can perform operations in real time, near real time, or batch mode.

[0043] Network interface device(s) 1112 enable computing system 1100 to broker data within network 1114 with entities external to computing system 1100 via any communication protocol supported by computing system 1100 and the external entities. Examples of network interface devices 1112 include network adapter cards, wireless network interface cards, routers, access points, wireless routers, switches, multi-layer switches, protocol converters, gateways, bridges, bridge routers, hubs, digital media receivers, and / or repeaters, as well as all wireless elements described herein.

[0044] Memory (e.g., main memory 1106, non-volatile memory 1110, machine-readable medium 1126) can be local, remote, or distributed. While depicted as a single medium, machine-readable medium 1126 can include multiple media (e.g., centralized / distributed databases and / or associated caches and servers) that store one or more sets of instructions 1128. Machine-readable (storage) medium 1126 can include any medium capable of storing, encoding, or carrying a set of instructions for execution by computing system 1100. Machine-readable medium 1126 can be non-transitory or can include a non-transitory device. In this regard, non-transitory storage media can include tangible devices, i.e., devices have a concrete physical form, but the devices can change their physical state. Thus, for example, non-transitory refers to a device that remains tangible despite this change in state.

[0045] While implementations have been described in the context of fully functional computing devices, various examples may be distributed as program products in various forms. Examples of machine-readable storage media, machine-readable media, or computer-readable media include recordable-type media such as volatile and non-volatile memory devices 1110, removable flash memory, hard disk drives, optical disks, and transmission-type media such as digital and analog communications links.

[0046] Generally, the routines executed to implement the examples herein may be implemented as part of an operating system or a specific application, component, program, object, module, or sequence of instructions (collectively referred to as a "computer program"). A computer program typically includes one or more instructions (e.g., instructions 1104, 1108, 1128) that are configured at various times in various memory and storage devices within a computing device. When read and executed by processor 1102, the instructions cause computing system 1100 to perform operations to implement elements including various aspects of the present disclosure.

[0047] It is therefore understood that the disclosed techniques can be implemented in an IMS to provide modularity and uniformed communication between the IMS and other network functions in a 5G or future generation wireless communication network, thereby enabling increased efficiency and reduced complexity in signaling, monitoring, and deployment.

[0048] remarks

[0049] The description and associated drawings are illustrative examples and should not be construed as limiting. The present disclosure provides specific details for a thorough understanding and enabling description of these examples. However, those skilled in the relevant art will understand that the invention may be practiced without many of these details. Likewise, those skilled in the relevant art will understand that the invention may include well-known structures or features that have not been shown or described in detail to avoid unnecessarily obscuring the description of the examples.

[0050] The terms "example," "embodiment," and "implementation" are used interchangeably. For example, references to "one example" or "an example" in this disclosure can, but do not necessarily, refer to the same implementation. Such references refer to at least one of the implementations. Appearances of the phrase "in one example" do not necessarily all refer to the same example, nor are they mutually exclusive separate or alternative examples from other examples. Features, structures, or characteristics described in connection with an example may be included in other examples of the disclosure. Furthermore, various features are described that may be exhibited by some examples and not by other examples. Similarly, various requirements are described that may be requirements of some examples but not other examples.

[0051] The terms used in this specification should be interpreted in the broadest reasonable manner, even though they are used in connection with specific embodiments of the present invention. Terms used in this disclosure generally have their ordinary meanings in the relevant technical field, within the context of this disclosure, and in the specific context in which each term is used. The description of alternative language or synonyms does not exclude the use of other synonyms. No particular importance should be placed on whether a term is detailed or discussed in this specification. The use of highlighting does not affect the scope and meaning of a term. Furthermore, it will be understood that the same thing can be said in more than one way.

[0052] Unless the context clearly dictates otherwise, throughout the specification and claims, words like "comprise," "including," and the like should be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense. That is, they mean "including, but not limited to." As used herein, the terms "connected," "coupled," or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, where the coupling or connection between elements may be physical, logical, or a combination thereof. Furthermore, the words "herein," "above," "below," and words of similar import may refer to this application as a whole and not to specific portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural may also include the plural or singular, respectively. The word "or" in connection with a list of two or more items encompasses all of the following interpretations of that word: any of the items in the list, all of the items in the list, and any combination of the items in the list. The term "module" broadly refers to a software component, firmware component, and / or hardware component.

[0053] While specific examples of techniques are described above for illustrative purposes, those skilled in the art will recognize that various equivalent modifications are possible within the scope of the invention. For example, while processes or blocks are presented in a given order, alternative implementations may perform routines or use systems having blocks in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and / or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks may be shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Furthermore, any specific numbers described herein are merely examples, as alternative implementations may use different values ​​or ranges.

[0054] The details of the disclosed implementations may vary considerably in particular implementations, while still encompassed by the disclosed teachings. As noted above, specific terms used when describing features or aspects of the present invention should not be interpreted as meaning that the terms are redefined herein to be limited to any particular characteristic, feature, or aspect of the invention to which they relate. In general, the terms used in the following claims should not be interpreted as limiting the invention to the specific examples disclosed herein, unless the detailed description above explicitly defines such terms. Thus, the actual scope of the present invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the scope of the claims. Some alternative implementations may include additional elements or fewer elements than the implementations described above.

[0055] Any patents and applications and other references mentioned above, and any patents and applications and other references that may be listed in accompanying filing papers, are incorporated herein by reference in their entirety, except for any disclaimer or disclaimer of subject matter, and except to the extent the incorporated material contradicts the explicit disclosure of this specification, in which case the language of this disclosure will control. Aspects of the present invention can be modified to employ the systems, functions, and concepts of the various references discussed above to provide further implementations of the present invention.

[0056] To reduce the number of claims, certain implementation aspects are presented below in certain claim forms, but the applicant contemplates various aspects of the invention in other forms. For example, claimed aspects may be recited in means-plus-function form or in other forms, such as embodied in a computer-readable medium. Claims intended to be interpreted as means-plus-function claims use the term "means for." However, the use of the term "for" in any other context is not intended to invoke a similar interpretation. The applicant reserves the right to pursue such additional claim forms in either the present application or any continuing applications.

Claims

1. 1. A method for wireless communication, comprising: sending, by a Media Resource Function (MRF) node in an Internet Protocol (IP) Multimedia Subsystem (IMS), a registration request to a Network Function Repository Function (NRF) over an Nnrf interface; the MRF node is capable of supporting a service-based architecture; the registration request includes a profile of the MRF node; the profile includes capability information of the MRF node indicating one or more services supported by the MRF node; Steps: receiving, by the MRF node, a registration response from the NRF acknowledging the registration request; and the one or more services include at least one of an audio announcement service, an audio conferencing service, an audio codec adaptation service, a video codec adaptation service, or a video conferencing service; method.

2. The method of claim 1 , wherein the registration request further includes location information associated with the media service.

3. The method of claim 1 , wherein the registration request is a Nnrf_NFManagement_NFRegister request message.

4. The method of claim 1 , wherein the registration response is a Nnrf_NFManagement_NFRegister response message.

5. 1. A method for wireless communication, comprising: sending, by a node capable of supporting a service-based architecture in an Internet Protocol (IP) Multimedia Subsystem (IMS), a discovery request to a Network Function Repository Function (NRF) over an Nnrf interface; the discovery request includes information about one or more services; Steps: receiving, by the node, a response from the NRF; the response indicating one or more Media Resource Function (MRF) nodes that support the one or more services. Steps: and the one or more services include at least one of an audio announcement service, an audio conferencing service, an audio codec adaptation service, a video codec adaptation service, or a video conferencing service; method.

6. The method of claim 5 , wherein the discovery request is a Nnrf_NFDiscover_request message.

7. The method of claim 5 , wherein the response is a Nnrf_NFDiscover_Request response message.

8. 1. An apparatus for wireless communication implemented as a Media Resource Function (MRF) node in an Internet Protocol (IP) Multimedia Subsystem (IMS), comprising: at least one processor, the processor causing the apparatus to: sending a registration request to a Network Function Repository Function (NRF) via an Nnrf interface; the MRF node is capable of supporting a service-based architecture; the registration request includes a profile of the MRF node; the profile includes capability information of the MRF node indicating one or more services supported by the MRF node; Steps: receiving a registration response from the NRF confirming the registration request; and the one or more services comprise at least one of an audio announcement service, an audio conferencing service, an audio codec adaptation service, a video codec adaptation service, or a video conferencing service; Device.

9. The apparatus of claim 8 , wherein the registration request further includes location information associated with the media service.

10. The apparatus of claim 8 , wherein the registration request is a Nnrf_NFManagement_NFRegister request message.

11. The apparatus of claim 8 , wherein the registration response is a Nnrf_NFManagement_NFRegister response message.

12. 1. A node capable of supporting a service-based architecture in an Internet Protocol (IP) Multimedia Subsystem (IMS), comprising: at least one processor, said processor causing said node to: sending a discovery request to a Network Function Repository Function (NRF) over an Nnrf interface; the discovery request includes information about one or more services. Steps: receiving a response from the NRF, the response indicating one or more Media Resource Function (MRF) nodes that support one or more services. Steps: and the one or more services include at least one of an audio announcement service, an audio conferencing service, an audio codec adaptation service, a video codec adaptation service, or a video conferencing service; node.

13. The node of claim 12 , wherein the discovery request is a Nnrf_NFDiscover_request message.

14. The node of claim 12 , wherein the response is a Nnrf_NFDiscover_Request response message.

Images