EP4000287A1 - Mécanisme pour faciliter un trafic de signalisation - Google Patents
Mécanisme pour faciliter un trafic de signalisationInfo
- Publication number
- EP4000287A1 EP4000287A1 EP20751456.3A EP20751456A EP4000287A1 EP 4000287 A1 EP4000287 A1 EP 4000287A1 EP 20751456 A EP20751456 A EP 20751456A EP 4000287 A1 EP4000287 A1 EP 4000287A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- service
- function
- network function
- proxy
- producer
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 230000011664 signaling Effects 0.000 title description 7
- 230000007246 mechanism Effects 0.000 title description 5
- 230000006870 function Effects 0.000 claims abstract description 192
- 230000004044 response Effects 0.000 claims abstract description 49
- 238000000034 method Methods 0.000 claims abstract description 32
- 230000015654 memory Effects 0.000 claims abstract description 27
- 238000004590 computer program Methods 0.000 claims abstract description 19
- 238000013507 mapping Methods 0.000 claims abstract description 17
- 238000012546 transfer Methods 0.000 claims description 5
- 238000010200 validation analysis Methods 0.000 claims description 4
- 238000004891 communication Methods 0.000 description 27
- 238000007726 management method Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 239000000835 fiber Substances 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 description 2
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 238000013499 data model Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4541—Directories for service discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
Definitions
- the examples and non-limiting embodiments relate generally to communications and, more particularly, to a mechanism to facilitate signaling traffic.
- an apparatus includes at least one processor, at least one non-transitory memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform: updating a profile comprising data associated with a producer network function in response to a registration request of the producer network function by adding a token identifier to a service identifier associated with a service of the producer network function; forwarding the updated profile to a network function repository function, wherein at least one internet protocol address is updated so that a proxy function is an endpoint for use of the service; storing and maintaining a mapping between the token identifier and the service of the producer network function; and providing the updated profile to a consumer network function in response to a discovery request for the service.
- a non-transitory program storage device readable by a machine may be provided, the non-transitory program storage device readable by a machine tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising: updating a profile comprising data associated with a producer network function in response to a registration request of the producer network function by adding a token identifier to a service identifier associated with a service of the producer network function; forwarding the updated profile to a network function repository function, wherein at least one internet protocol address is updated so that a proxy function is an endpoint for use of the service; storing and maintaining a mapping between the token identifier and the service of the producer network function; and providing the updated profile to a consumer network function in response to a discovery request for the service.
- an apparatus includes means for updating a profile comprising data associated with a producer network function in response to a registration request of the producer network function by adding a token identifier to a service identifier associated with a service of the producer network function; means for forwarding the updated profile to a network function repository function, wherein at least one internet protocol address is updated so that a proxy function is an endpoint for use of the service; means for storing and maintaining a mapping between the token identifier and the service of the producer network function; and means for providing the updated profile to a consumer network function in response to a discovery request for the service.
- a method includes updating a profile comprising data associated with a producer network function in response to a registration request of the producer network function by adding a token identifier to a service identifier associated with a service of the producer network function; forwarding the updated profile to a network function repository function, wherein at least one internet protocol address is updated so that a proxy function is an endpoint for use of the service; storing and maintaining a mapping between the token identifier and the service of the producer network function; and providing the updated profile to a consumer network function in response to a discovery request for the service.
- FIG. 1 is a block diagram of one possible and non limiting system in which the example embodiments may be practiced.
- FIG. 2 illustrates an example configuration of a network function proxy ("NF Proxy") .
- FIG. 3 illustrates an example unit of deployment of a NF Proxy.
- eNB or eNodeB evolved Node B (e.g., an LTE base station)
- En-gNB node providing NR user plane and control plane protocol
- E-UTRA evolved universal terrestrial radio access, i.e., the LTE radio access technology
- gNB or gNodeB base station for 5G/NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC
- IPv4 internet protocol version 4 (or internet protocol version 6)
- UE user equipment e.g., a wireless, typically mobile device
- FIG. 1 shows a block diagram of one possible and non-limiting example in which the examples may be practiced.
- a user equipment (UE) 110 radio access network (RAN) node 170, and network element (s) 190 are illustrated.
- the user equipment (UE) 110 is in wireless communication with a wireless network 100.
- a UE is a wireless device that may access the wireless network 100.
- the UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127.
- Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133.
- the one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like.
- the one or more transceivers 130 are connected to one or more antennas 128.
- the one or more memories 125 include computer program code 123.
- the UE 110 includes a module 140, comprising one of or both parts 140-1 and/or 140-2, which may be implemented in a number of ways.
- the module 140 may be implemented in hardware as module 140-1, such as being implemented as part of the one or more processors 120.
- the module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array.
- the module 140 may be implemented as module 140-2, which is implemented as computer program code 123 and is executed by the one or more processors 120.
- the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein.
- the UE 110 communicates with RAN node 170 via a wireless link 111.
- the RAN node 170 in this example is a base station that provides access by wireless devices such as the UE 110 to the wireless network 100.
- the RAN node 170 may be, for example, a base station for 5G, also called New Radio (NR) .
- the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or an ng-eNB.
- a gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (such as, for example, the network element (s) 190).
- the ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC.
- the NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs) , of which DU 195 is shown.
- the DU may include or be coupled to and control a radio unit (RU) .
- the gNB-CU is a logical node hosting radio resource control (RRC) , SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs.
- RRC radio resource control
- the gNB-CU terminates the FI interface connected with the gNB-DU.
- the FI interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195.
- the gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU.
- One gNB-CU supports one or multiple cells.
- One cell is supported by only one gNB-DU.
- the gNB-DU terminates the FI interface 198 connected with the gNB-CU.
- the DU 195 is considered to include the transceiver 160, e.g., as part of a RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195.
- the RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution) , or any other suitable base station or node.
- eNB evolved NodeB
- the RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157.
- Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163.
- the one or more transceivers 160 are connected to one or more antennas 158.
- the one or more memories 155 include computer program code 153.
- the CU 196 may include the processor (s) 152, memories 155, and network interfaces 161.
- the DU 195 may also contain its own memory/memories and processor ( s ) , and/or other hardware, but these are not shown.
- the RAN node 170 includes a module 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways.
- the module 150 may be implemented in hardware as module 150-1, such as being implemented as part of the one or more processors 152.
- the module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array.
- the module 150 may be implemented as module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152.
- the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein.
- the functionality of the module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.
- the one or more network interfaces 161 communicate over a network such as via the links 176 and 131.
- Two or more gNBs 170 may communicate using, e.g., link 176.
- the link 176 may be wired or wireless or both and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards .
- the one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like.
- the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH/DU, and the one or more buses 157 may be implemented in part as, for example, fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit (CU) , gNB-CU) of the RAN node 170 to the RRH/DU 195.
- Reference 198 also indicates those suitable network link(s).
- the cell makes up part of a base station. That is, there may be multiple cells per base station. For example, there may be three cells for a single carrier frequency and associated bandwidth, each cell covering one-third of a 360 degree area so that the single base station' s coverage area covers an approximate oval or circle. Furthermore, each cell may correspond to a single carrier and a base station may use multiple carriers. So if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells.
- the wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a further network, such as a telephone network and/or a data communications network (e.g., the Internet).
- a further network such as a telephone network and/or a data communications network (e.g., the Internet).
- core network functionality for 5G may include access and mobility management function(s) (AMF(S)) and/or user plane functions (UPF(s)) and/or session management function(s) (SMF(s)).
- AMF(S) access and mobility management function(s)
- UPF(s) user plane functions
- SMF(s) session management function
- Such core network functionality for LTE may include MME (Mobility Management Entity) /SGW (Serving Gateway) functionality. These are merely example functions that may be supported by the network element (s) 190, and note that both 5G and LTE functions might be supported.
- the RAN node 170 is coupled via a link 131 to the network element 190.
- the link 131 may be implemented as, e.g., an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards.
- the network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185.
- the one or more memories 171 include computer program code 173.
- the one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.
- the wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network.
- Network virtualization involves platform virtualization, often combined with resource virtualization.
- Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects .
- the computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
- the computer readable memories 125, 155, and 171 may be means for performing storage functions.
- the processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples.
- the processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, network element (s) 190, and other functions as described herein.
- the various embodiments of the user equipment 110 may include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.
- cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.
- PDAs personal digital assistants
- portable computers having wireless communication capabilities
- image capture devices such as digital cameras having wireless communication capabilities
- gaming devices having wireless communication capabilities
- music storage and playback appliances having wireless communication capabilities
- SBA service based architecture
- NFs SBA Network Functions
- NRF NF Repository Function
- Rel. 15 it is specified that each NF is to contact the NRF and further NFs directly. This, however, is not really feasible in real deployments. Therefore, Rel. 16 introduces a "service communication proxy" (SCP) .
- SCP service communication proxy
- the 5G system architecture enables each network function and its network function services to interact with other NF and its Network Function Services directly or indirectly via the SCP (e.g. , Rel. 16 TS 23.501) .
- the functionality of the SCP is not yet defined.
- the disclosure herein describes an entity or function that may be inserted without any changes to the behavior of NFs and NRF.
- This function may for example be called network function proxy (NF Proxy) or network function repository function proxy (NRF Proxy) .
- NF Proxy network function proxy
- NRF Proxy network function repository function proxy
- the entity or function is referred to as the NF Proxy.
- the NF Proxy is transparent to all further entities, such as further 3GPP entities. As the NF Proxy is transparent, this concept may be used already for current (e.g. Rel. 15) networks.
- Function endpoints of the NF Proxy are configured as the NRFs . All NRF traffic then lands at the new function. During registration of a NF service the new function updates or manipulates the NF Profile such that the respective IP addresses may lead to the new function. In one implementation example, the function adds an identifier (a "magic token") to the hyper text transfer protocol (HTTP) universal resource identifier (URI) prefix of the service. The NF Proxy maintains a mapping between the identifier and the service. The manipulated service registration request may be forwarded to the NRF. When a service consumer performs service discovery at the NRF, the service consumer may receive the manipulated NF profile. The service consumer may, thus, subsequently contact the NF Proxy. The NF Proxy knows from the identifier (in the prefix) which service the consumer actually requests. The NF Proxy may forward the traffic accordingly. Also, all further traffic may go through the NF Proxy.
- HTTP hyper text transfer protocol
- URI universal resource identifier
- NRF is a network service in the 5G core which acts as a registrar of all the network functions operating in the 5G core.
- a communication proxy is a network function in the 5G core that facilitates routing of 5G HTTP2 signalling traffic.
- the communication proxy also provides additional capabilities such as interworking, mediation, rate limiting, load balancing etc.
- the communication proxy ensures that the complexity of the 5GC is reduced by having a single consolidate point of contact for all the network functions.
- NRF and the communication proxy may be deployed independently.
- 5G Core Network includes a large number of services and service instances. Since a single point of contact is the communication proxy, the communication proxy may have the visibility of all the network functions. A problem may arise from the fact that individual NFs are registered directly onto the NRF. In an SBA, a consumer service or a NF may discover the producer services from the NRF through a discovery procedure defined as per 3GPP TS 29510 specification. In this kind of a discovery procedure, the communication proxy is not in the path of the signalling. This procedure negates the advantages a communication proxy may bring into a 5GC.
- features as described herein may be used to provide a method and apparatus to resolve the issue of the communication proxy not being in the signalling path between any NFs. This may be achieved by:
- the NF Proxy may intercept and influence all interactions of NFs and NRFs ;
- a NF profile is the data model which describes the capability and the endpoint definitions of each NF that registers with the NRF.
- the NF Proxy provides means to intercept and interpret the NF profile if required. The NF Proxy achieves this by manipulating the NF profile during registration prior to forwarding the request to the NRF.
- NF Proxy endpoints as the NRFs in 5GC.
- the NRF traffic hence lands on the NF Proxy and then gets proxied to the actual NRF. This provides the NF Proxy an opportunity to manipulate the service details during the registration procedure of a NF.
- the NF Proxy prefixes a magic token to the HTTP URI prefix for each of the services. This token may uniquely identify each instance of a registered service.
- the NF Proxy maintains a mapping between the token and the service instance.
- the IP addresses (such as internet protocol version 4 (IPv4) & internet protocol version 6 (IPv6) addresses) may be manipulated to expose NF Proxy endpoints. Hence, the actual NF profile details that get registered with the NRF may have the NF Proxy endpoint for service consumption.
- a consumer service when it contacts the NRF for service details of a producer, the consumer service may receive the NF profiles with:
- the consumer NF may contact the NF Proxy with the prepended service URI .
- the NF Proxy may now identify the actual destination service instance using the magic token in the URI. This may ensure that further traffic may flow through the NF Proxy.
- FIG. 2 illustrates an example configuration 200 of a NF Proxy.
- the NF Proxy 204 is in the signaling path of a consumer NF 202 and a producer NF 208.
- the NF Proxy 204 acts as a transparent proxy for the NRF 206. Illustrated in FIG. 2 is the process 210 of registration of the producer NF 208 as well as the process 230 of the consumer NF 202 discovering the producer NF 208.
- An example process 210 of registration of the producer NF 208 proceeds as follows.
- the producer NF 208 initiates a registration request, which as shown includes the parameters nfinstancelD and NFProfile.
- the parameter NFProfile corresponds to the NF Profile, or the data model which describes the capability and the endpoint definitions of the producer NF 208.
- the registration request is implemented at 214 as an HTTP2 PUT method.
- the NF Proxy 204 updates the NF Profile to point to the NF Proxy 204, and prepends the URI with the magic token.
- the NF Proxy 204 forwards the registration request to the NRF 206.
- the forwarding of the registration request by the NF Proxy 204 to the NRF 206 is implemented at 220 as an HTTP2 PUT method such that the IPs (e.g., IPv4 and IPv6 addresses) are updated so that the endpoints of the NF Proxy 204 is (e.g., is a proxy for) the NRF 206.
- the magic token is also provided to the NRF 206 via the registration request forwarding.
- the service details are stored with the NRF 206, and at 224 the NRF 206 provides a success indication to the NF Proxy 204 via a status response code.
- the status response code is an HTTP2 201 Created code.
- the NF Proxy 204 stores a mapping between the magic token and the service instance being provided by the producer NF 208.
- the NF Proxy 204 provides a success indication to the producer NF 208 via a status response code such as an HTTP2 201 Created code .
- An example process 230 by which the consumer NF 202 discovers the producer NF 208 proceeds as follows.
- the consumer NF 202 initiates a discovery procedure to contact the NRF 206 for service details of a producer, or to discover the producer NF 208.
- the NF Proxy 204 has intercepted the discovery procedure initiated by the consumer NF 202 at 232.
- the NF Proxy 204 indicates to the consumer NF 202 to contact the NF Proxy 204 to perform the discovery request.
- the NF Proxy 204 forwards the discovery procedure to discover the producer NF 208 to the NRF 206.
- the lookup service details response may point to the NF Proxy 204.
- the NRF 206 may forward a contact NF Proxy response to the NF Proxy 204.
- the NF Proxy 204 updates discovery details, and at 244, the NF Proxy 204 forwards a contact NF Proxy response to the consumer NF 202.
- the NF Proxy 204 may serve a service request from the consumer NF 202.
- the consumer NF 202 now knows to initiate a service request with the NF Proxy .
- the consumer NF 202 initiates a service request to the NF Proxy 204.
- the NF Proxy 204 may perform one or more of rate limiting, validation, and manipulation.
- the NF Proxy 204 finds the destination service instance. The destination is identified using the magic token present in the URI (inserted by the NF Proxy (the "NF-P") during registration) .
- the NF Proxy forwards the service request to the producer NF 208.
- the producer NF 208 provides a service response to the NF Proxy.
- the NF Proxy may perform one or more of rate limiting, validation, and manipulation.
- the NF Proxy 204 provides the service response via parameter NRx_xxx to the consumer NF 202.
- FIG. 3 illustrates an example unit of deployment 300 of a NF Proxy 302, including optional processor 304 and memory 306.
- the NF Proxy 302 may be deployed or implemented as a standalone unit, in which case the unit of deployment 300 has a processor 304 and memory 306 and the NF Proxy 302 includes computer program code to implement the functionality of the NF Proxy 302.
- the unit of deployment 300 may be either the UE 110, the RAN node 170, or the network element 190.
- the NF Proxy 302 is included in the computer program code 123.
- the NF Proxy 302 is included in the computer program code 153.
- the NF Proxy 302 is included in the computer program code 173.
- the unit of deployment 300 may in various ways be combined with, or meshed with, other functions or modules such as the consumer NF 202, producer NF 208, and/or the NRF 206 such as those shown in FIG. 2.
- the unit of deployment 300 may be deployed independently of the consumer NF 202, the producer NF 208, and the NRF 206.
- an apparatus may be provided that includes at least one processor, at least one non-transitory memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform: updating a profile comprising data associated with a producer network function in response to a registration request of the producer network function by adding a token identifier to a service identifier associated with a service of the producer network function; forwarding the updated profile to a network function repository function, wherein at least one internet protocol address is updated so that a proxy function is an endpoint for use of the service; storing and maintaining a mapping between the token identifier and the service of the producer network function; and providing the updated profile to a consumer network function in response to a discovery request for the service.
- a non-transitory program storage device readable by a machine may be provided, the non- transitory program storage device readable by a machine tangibly embodying a program of instructions executable by the machine for performing operations, the operations comprising: updating a profile comprising data associated with a producer network function in response to a registration request of the producer network function by adding a token identifier to a service identifier associated with a service of the producer network function; forwarding the updated profile to a network function repository function, wherein at least one internet protocol address is updated so that a proxy function is an endpoint for use of the service; storing and maintaining a mapping between the token identifier and the service of the producer network function; and providing the updated profile to a consumer network function in response to a discovery request for the service.
- an apparatus includes means for updating a profile comprising data associated with a producer network function in response to a registration request of the producer network function by adding a token identifier to a service identifier associated with a service of the producer network function; means for forwarding the updated profile to a network function repository function, wherein at least one internet protocol address is updated so that a proxy function is an endpoint for use of the service; means for storing and maintaining a mapping between the token identifier and the service of the producer network function; and means for providing the updated profile to a consumer network function in response to a discovery request for the service.
- a method may be provided that includes updating a profile comprising data associated with a producer network function in response to a registration request of the producer network function by adding a token identifier to a service identifier associated with a service of the producer network function; forwarding the updated profile to a network function repository function, wherein at least one internet protocol address is updated so that a proxy function is an endpoint for use of the service; storing and maintaining a mapping between the token identifier and the service of the producer network function; and providing the updated profile to a consumer network function in response to a discovery request for the service.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201962875697P | 2019-07-18 | 2019-07-18 | |
PCT/US2020/042708 WO2021011933A1 (fr) | 2019-07-18 | 2020-07-20 | Mécanisme pour faciliter un trafic de signalisation |
Publications (2)
Publication Number | Publication Date |
---|---|
EP4000287A1 true EP4000287A1 (fr) | 2022-05-25 |
EP4000287B1 EP4000287B1 (fr) | 2023-10-18 |
Family
ID=71948791
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP20751456.3A Active EP4000287B1 (fr) | 2019-07-18 | 2020-07-20 | Mécanisme pour faciliter un trafic de signalisation |
Country Status (4)
Country | Link |
---|---|
US (1) | US11902389B2 (fr) |
EP (1) | EP4000287B1 (fr) |
CN (1) | CN114450982B (fr) |
WO (1) | WO2021011933A1 (fr) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114450982B (zh) * | 2019-07-18 | 2023-11-10 | 诺基亚通信公司 | 用于促进信令业务的装置、存储设备和方法 |
WO2021104636A1 (fr) * | 2019-11-28 | 2021-06-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Migration vers un mode de communication indirect dans une architecture à base de service |
US20220353263A1 (en) * | 2021-04-28 | 2022-11-03 | Verizon Patent And Licensing Inc. | Systems and methods for securing network function subscribe notification process |
US11888946B2 (en) | 2021-06-02 | 2024-01-30 | Oracle International Corporation | Methods, systems, and computer readable media for applying or overriding preferred locality criteria in processing network function (NF) discovery requests |
US11930083B2 (en) | 2021-08-09 | 2024-03-12 | Oracle International Corporation | Methods, systems, and computer readable media for processing network function (NF) discovery requests at NF repository function (NRF) using prioritized lists of preferred locations |
US11949734B2 (en) | 2021-08-17 | 2024-04-02 | Charter Communications Operating, Llc | Cloud native realization of distributed ran elements |
US11871309B2 (en) | 2021-09-28 | 2024-01-09 | Oracle International Corporation | Methods, systems, and computer readable media for network function discovery using preferred-locality information |
US11888957B2 (en) | 2021-12-07 | 2024-01-30 | Oracle International Corporation | Methods, systems, and computer readable media for locality and serving scope set based network function (NF) profile prioritization and message routing |
US11652895B1 (en) * | 2022-02-15 | 2023-05-16 | Oracle International Corporation | Methods, systems, and computer readable media for dynamic optimized network function discovery for consumer network functions |
Family Cites Families (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6886017B1 (en) * | 1999-04-30 | 2005-04-26 | Elata Limited | System and method for managing distribution of content to a device |
US7716077B1 (en) * | 1999-11-22 | 2010-05-11 | Accenture Global Services Gmbh | Scheduling and planning maintenance and service in a network-based supply chain environment |
US7057591B1 (en) * | 2001-07-11 | 2006-06-06 | Nokia Corporation | Advertising using an eBook with a bistable display |
JP4706542B2 (ja) * | 2006-04-10 | 2011-06-22 | 株式会社日立製作所 | 通信装置 |
KR100800867B1 (ko) * | 2006-09-12 | 2008-02-04 | 삼성전자주식회사 | 이종 망에서 핸드오버 지연 감소 방법 및 장치 |
WO2008072093A2 (fr) * | 2006-12-13 | 2008-06-19 | Quickplay Media Inc. | Plate-forme multimédia mobile |
US8788597B2 (en) * | 2009-03-24 | 2014-07-22 | Barracuda Networks, Inc. | Recalling spam email or viruses from inboxes |
US8762288B2 (en) * | 2009-04-22 | 2014-06-24 | The Western Union Company | Methods and systems for establishing an identity confidence database |
US20120036494A1 (en) * | 2010-08-06 | 2012-02-09 | Genwi, Inc. | Web-based cross-platform wireless device application creation and management systems, and methods therefor |
US8832433B2 (en) * | 2012-08-17 | 2014-09-09 | Cellco Partnership | Methods and systems for registering a packet-based address for a mobile device using a fully-qualified domain name (FQDN) for the device in a mobile communication network |
US9007945B2 (en) * | 2013-01-23 | 2015-04-14 | Dell Products L.P. | Automated network service discovery and communication |
EP2948933B1 (fr) * | 2013-01-24 | 2017-03-08 | Roger Andre Eilertsen | Système de guidage et de surveillance de trafic |
JP6765373B2 (ja) | 2014-12-24 | 2020-10-07 | コニンクリーケ・ケイピーエヌ・ナムローゼ・フェンノートシャップ | オン・デマンドのサービス・プロビジョニングを制御するための方法 |
HUE046372T2 (hu) | 2017-05-08 | 2020-03-30 | Ntt Docomo Inc | Eljárás hálózati funkcióknak mobil rádiós kommunikációs hálózat hálózati szeletpéldányaival való társításához |
JP7200237B2 (ja) * | 2017-10-13 | 2023-01-06 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | 異なるアーキテクチャ間のプロキシのための方法および装置 |
WO2019076801A1 (fr) | 2017-10-17 | 2019-04-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Enregistrement et découverte de service dans un réseau de communication |
WO2019076634A1 (fr) * | 2017-10-17 | 2019-04-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Enregistrement de service dans un réseau de communication |
WO2020099958A1 (fr) * | 2018-11-16 | 2020-05-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Gestion efficace d'abonnements |
US11064321B2 (en) * | 2018-12-29 | 2021-07-13 | Intel Corporation | Content centric dynamic ad hoc networking |
US20230079238A1 (en) * | 2019-01-03 | 2023-03-16 | Lucomm Technologies, Inc. | Flux System |
CN114450982B (zh) * | 2019-07-18 | 2023-11-10 | 诺基亚通信公司 | 用于促进信令业务的装置、存储设备和方法 |
US11405400B2 (en) * | 2019-09-08 | 2022-08-02 | Microsoft Technology Licensing, Llc | Hardening based on access capability exercise sufficiency |
CN115152320A (zh) * | 2020-02-17 | 2022-10-04 | 三星电子株式会社 | 无线通信系统中用于增强网络选择准确性的方法和装置 |
US11283883B1 (en) * | 2020-11-09 | 2022-03-22 | Oracle International Corporation | Methods, systems, and computer readable media for providing optimized binding support function (BSF) packet data unit (PDU) session binding discovery responses |
US11425636B1 (en) * | 2021-04-16 | 2022-08-23 | Nokia Technologies Oy | Network function service subscription control |
US11570689B2 (en) * | 2021-05-07 | 2023-01-31 | Oracle International Corporation | Methods, systems, and computer readable media for hiding network function instance identifiers |
US20230188963A1 (en) * | 2021-12-13 | 2023-06-15 | Oracle International Corporation | METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR REDUCING INTER-PUBLIC LAND MOBILE NETWORK (PLMN) FORWARDING OF MESSAGES RELATING TO Nnrf SERVICE OPERATIONS |
US11564266B1 (en) * | 2022-07-11 | 2023-01-24 | Starkeys Llc | Permission-based controlling network architectures and systems, having cellular network components and elements modified to host permission controlling schemas designed to facilitates electronic peer-to-peer communication sessions methods for use thereof |
US20230300111A1 (en) * | 2022-03-15 | 2023-09-21 | Centurylink Intellectual Property Llc | System and method for network-connected device security |
US11743363B1 (en) * | 2022-05-23 | 2023-08-29 | Oracle International Corporation | Methods, systems, and computer readable media for utilizing network function (NF) service attributes associated with registered NF service producers in a hierarchical network |
-
2020
- 2020-07-20 CN CN202080065456.XA patent/CN114450982B/zh active Active
- 2020-07-20 EP EP20751456.3A patent/EP4000287B1/fr active Active
- 2020-07-20 US US17/597,660 patent/US11902389B2/en active Active
- 2020-07-20 WO PCT/US2020/042708 patent/WO2021011933A1/fr unknown
Also Published As
Publication number | Publication date |
---|---|
EP4000287B1 (fr) | 2023-10-18 |
CN114450982B (zh) | 2023-11-10 |
CN114450982A (zh) | 2022-05-06 |
US20220272165A1 (en) | 2022-08-25 |
WO2021011933A1 (fr) | 2021-01-21 |
US11902389B2 (en) | 2024-02-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP4000287B1 (fr) | Mécanisme pour faciliter un trafic de signalisation | |
EP3886502B1 (fr) | Appareil, procédé et support lisible par ordinateur associés à des informations concernant scp(s) et sepp(s) stockés dans nrf | |
CN114430897B (zh) | 用于边缘解析功能的方法、装置和系统 | |
CN111295922B (zh) | 常驻协议数据单元会话的处理方法及其装置 | |
US10778780B2 (en) | Apparatus and method for controlling connection in communication system | |
EP3476100B1 (fr) | Sélection de version ip | |
CN111837371A (zh) | 基于增强mptcp的应用移动性 | |
EP3788766A1 (fr) | Équipement utilisateur direct à un équipement utilisateur sans identifiant d'accès au réseau de données | |
EP3550886B1 (fr) | Session entrante de voix sur ims | |
JP7035082B2 (ja) | ユーザプレーンリンク確立方法、基地局、およびモビリティ管理デバイス | |
KR20220144389A (ko) | 에지 컴퓨팅 서버들의 효율적인 발견 | |
EP4132100A1 (fr) | Procédé et dispositif de fourniture d'informations d'un réseau de données local à un terminal dans un système de communication sans fil | |
TW201406105A (zh) | 室外無線數據裝置與其訊號處理方法 | |
JP2021520657A (ja) | システム、移動体通信ネットワーク構成要素、ネットワーク機能を選択するための方法及びネットワーク機能を登録するための方法 | |
CN110557846A (zh) | 一种数据传输方法、终端设备及网络设备 | |
CN115735369A (zh) | 确定默认网络切片 | |
US20240022469A1 (en) | Method for determining edge configuration server and apparatus | |
CN116097751A (zh) | 利用smf重新选择来重新锚定 | |
JP7013423B2 (ja) | ハンドオーバーでのアップリンクベアラーバインディング | |
US11930547B2 (en) | MPTCP friendly cellular multi-connectivity architecture with transparent proxy | |
US12021827B2 (en) | Apparatus, method and computer program to influence 3GPP terminals on preferences between multiple recursive DNS servers | |
RU2783588C2 (ru) | Способ конфигурации сети и устройство связи | |
WO2023246104A1 (fr) | Procédé de communication et appareil associé | |
WO2023151491A1 (fr) | Procédé, dispositif et système de demande de fonction d'application | |
EP4262244A1 (fr) | Procédé et dispositif de détermination de point d'accès mec |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20220218 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20221214 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602020019483 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04W0004200000 Ipc: H04W0004000000 Ref country code: DE Ref legal event code: R079 Free format text: PREVIOUS MAIN CLASS: H04W0004200000 Ipc: H04W0004000000 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 61/4541 20220101ALI20230426BHEP Ipc: H04W 4/00 20180101AFI20230426BHEP |
|
INTG | Intention to grant announced |
Effective date: 20230525 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602020019483 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20231018 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1623548 Country of ref document: AT Kind code of ref document: T Effective date: 20231018 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240119 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240218 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240218 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240119 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240118 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240219 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240118 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20240530 Year of fee payment: 5 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231018 |