KR20180022565A - Communication method and apparatus for supporting non-ue associated signaling - Google Patents

Abstract

Disclosed are a communication method and apparatus for supporting non-UE associated signaling. The communication method of an IRF performing communication with a source network function and a destination network function comprises the steps of: receiving a message including a binding key from the source network function and an identifier of the destination network function; determining whether the destination network function is present in a local-PLMN corresponding to the IRF based on the identifier of the destination network function; looking up a binding between the binding key and an interface layer identity of the destination network function in an internal repository of the IRF when the destination network function is present in the local-PLMN; and transmitting a message to the destination network function using the binding when the binding is present in the internal repository.

Description

[0001] COMMUNICATION METHOD AND APPARATUS FOR SUPPORTING NON-UE ASSOCIATED SIGNALING [0002]

The following description relates to a communication method and apparatus for supporting non-UE related signaling, and more particularly, to a method and apparatus for dynamic configuration and routing (hereinafter referred to as " routing ") in connection establishment of a network function To a non-UE associated signaling routing in an Interconnecting and Routing Function (IRF) that enables a non-UE associated signaling routing.

In LTE, network functions or network element connections are provided mainly through OAM static configuration. However, in 5G core network, more adaptable structure is being developed and IRF Providing through a centralized routing entity is one approach. However, in the existing IRF technology, since the ID associated with the UE is assumed to be the NF-to-NF connection binding key value, non-UE association signaling can not use the corresponding structure.

The present invention can increase utility by allowing non-UE association signaling to be routable in an IRF that enables dynamic configuration and routing when establishing a connection between network functions in a mobile core network.

A communication method of an IRF for performing communication with a source network function (source NF) and a destination network function (destination NF) according to an exemplary embodiment includes receiving a binding key from the source network function and the destination network function The method comprising: receiving a message including an identifier of the mobile terminal; Determining whether the destination network function is in a local-PLMN corresponding to the IRF based on an identifier of the destination network function; Looking up a binding between the binding key and an interface layer identity of the destination network function in an internal repository of the IRF if the destination network function is present in the local-PLMN; And transmitting the message to the destination network function using the binding if the binding exists in the internal repository.

In a communication method according to an embodiment, the binding key may be information that enables the destination network function to uniquely locate a non-UE associated signaling session while receiving and processing the message.

In the communication method according to an exemplary embodiment, the binding key may be information independent of the UE session ID.

In a communication method according to an exemplary embodiment, the binding key may include an access network node ID.

In a communication method according to an embodiment, the non-UE association signaling session may be a global RAN ID signaling session for a specific RAN only.

The method may further include selecting an instance of the destination network function based on load / overload information if the binding does not exist in the internal storage; And sending the message to an instance of the selected destination network function.

The communication method according to an embodiment may further include updating the internal storage using an instance of the selected destination network function and a binding between the binding keys.

A communication method according to an exemplary embodiment of the present invention includes: confirming an identifier of an IRF in the remote-PLMN when the destination network function exists in the remote-PLMN; Updating an internal binding of the message to point to an IRF in the remote-PLMN for the destination network capability; And sending the message to an IRF in the remote-PLMN.

According to one embodiment, in an IRF that enables dynamic configuration and routing when establishing a connection between network functions in a mobile core network, non-UE association signaling can also be made routable to increase utility.

1 is a diagram illustrating a non-roaming reference model for interconnecting network functions according to one embodiment.
2 is a diagram illustrating a roaming reference model for interconnecting network functions according to one embodiment.
3 illustrates a binding storage of an IRF according to one embodiment.
4 is a diagram illustrating a communication method of routing messages between NF1 and NF4 according to an exemplary embodiment of the present invention.
5 is a diagram illustrating a communication method of routing a message between NF1 and NF4 according to another embodiment.
6 is a diagram illustrating an NF binding management method of an IRF according to an exemplary embodiment of the present invention.

Specific structural or functional descriptions of embodiments are set forth for illustration purposes only and may be embodied with various changes and modifications. Accordingly, the embodiments are not intended to be limited to the specific forms disclosed, and the scope of the disclosure includes changes, equivalents, or alternatives included in the technical idea.

The terms first or second, etc. may be used to describe various elements, but such terms should be interpreted solely for the purpose of distinguishing one element from another. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected or connected to the other element, although other elements may be present in between.

The singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprises ", or" having ", and the like, are used to specify one or more of the described features, numbers, steps, operations, elements, But do not preclude the presence or addition of steps, operations, elements, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the meaning of the context in the relevant art and, unless explicitly defined herein, are to be interpreted as ideal or overly formal Do not.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. The specific structural or functional descriptions below are illustrated for purposes of illustration only and are not to be construed as limiting the scope of the embodiments to those described in the text. Those skilled in the art will appreciate that various modifications and changes may be made thereto without departing from the scope of the present invention. In addition, the same reference numerals shown in the drawings denote the same members, and the well-known functions and structures are omitted.

1 and 2 are diagrams illustrating a reference model for interconnecting network functions according to an exemplary embodiment.

The present invention proposes a method for routing non-UE associated services in an IRF that enables dynamic configuration and routing when establishing a connection between network functions in a mobile core network. Since the non-UE association service can not perform the binding by distinguishing it by the UE session ID or the like, it can use any ID that can uniquely identify the corresponding signaling as the binding ID. For example, a non-UE association service associated with a particular access network node may use the access network node ID as the binding ID.

The present invention can be applied to the interconnection of network functions (NFs). The definition and functionalities of a network function can be assumed to be defined as solutions to other key issues.

When only one of the control plane access network functions is required to interface with only one of the control plane core network functions, the control plane access network function and the control plane core network function The interconnection model may be based on a point-to-point interface. For example, the control plane core network function 1 can interface with the control plane access network function 1 through a point-to-point interface. However, if it is determined that a plurality of control plane access network functions can directly interface with a plurality of control plane core network functions, the principles of the present invention include interfacing control plane access network functions and control plane core network functions Lt; / RTI >

Similarly, it is assumed that user plane core network functions are required to interface with each control plane core network functions. Therefore, the interconnection model between the user plane core network function and the control plane core network function may be based on a point-to-point interface. However, if any control plane functionality is allowed to interface with any user plane functionality, the principles of the present invention can be extended to interconnect control plane network functionality and user plane core network functionality.

The present invention may assume that multiple control plane core network functions are required to interact with a number of different control plane core network functions in a next generation core network architecture.

Unless expressly stated, the term "network function" may refer to a "control plane core network function" in the present invention. In order to understand the "control plane core network functions" of the EPC (Evolved Packet Core) context, the control plane of MME (Mobility Management Entity), PGW (PDW Gateway), Policy and Charging Rules Function (PCRF) ), A control plane of a TDF (Traffic Detection Function), a Traffic Steering Support Function (TSSF), a RAN Congestion Awareness Function (RCAF), and a Service Capability Enablement Function (SCEF).

Referring to FIG. 1, a non-roaming reference model for interconnection of network functions according to one embodiment is shown. Referring to FIG. 2, a roaming reference model for interconnection of network functions according to one embodiment is shown.

The roaming reference model may describe a scenario of a home routed traffic type. Other reference models (e.g., local breakout) may be derived here and are not shown here for the sake of simplicity.

1, NF1 represents the network function (NF) number 1, and NFn represents the network function (NF) number "n ". Rp1 denotes a reference point between a network function NF1 and an IRF (Interconnection & Routing Function), Rpn denotes a reference point between a network function NFn and an IRF (Interconnection & Routing Function), and Rpx denotes an inter- PLMN reference point (Inter-PLMN) reference point.

This reference point can be proposed as a 3GPP definition reference point. Not all messages supported at each reference point are the same. For example, some messages supported through Rp1 may be different from some messages supported via Rp2.

<High level principles>

The high level principles of Interconnection & Routing Function (IRF) based interconnection model can be as follows.

Each NF can interface with the IRF via a given reference point in its PLMN. The NFs do not interface directly with each other but can communicate with each other (e.g., send a request or response message) via the IRF. Thus, when needed, the interconnection model can allow any NF to communicate directly with any other NF without including other irrelevant network functions in the path. For example, NF1 can send messages to NF3 via IRF without NF2 if NF2 is not needed.

In the interconnect model, each NF can support only one reference point for IRF. All procedures for other NFs can be supported through this single reference point. For example, NF1 can support Rp1 towards IRF instead of Rpa towards NF2, Rpb towards NF4, and so on.

Since the NF does not need to maintain an interface layer association for each peer-NF in the network, a connectionless connection of the NF may result. However, the application layer state for a UE-associated or non-UE-associated session must be maintained. If the NF wants to change an instance (e.g., a virtual machine (VM) instance) for a given session (e.g., support for scale-in, scale-out and restoration features) The NF can update the IRF rather than the peer-NF. For example, NF1 can update IRF to a new instance number while moving Session 1 to Session 2 and not need to update NF2, NF3, NF4, etc. on the network.

Non-UE association signaling may include load, congestion or management association signaling (as described in GTP-C and S1AP in LTE).

IRF can be mainly responsible for message routing between NFs. The NF may determine the destination NF of the message and may be responsible for populating the message in the message header. The IRF may examine the message header to determine the interface layer identity (e.g., the instance number) of the destination NF for the session and route it to the appropriate NF. For routing purposes, the IRF may maintain a repository of the binding between the binding-key identity (e.g., UE identity) and the interface layer identity of the serving NFs.

If the procedure for a reference point between NF and IRF is generally defined, then this model may allow reuse of procedures by other NFs in the network. UE location change reporting "or" UE congestion level change reporting "without limiting that NF1 may invoke other NFs in the network, for example, , NF1 can be invoked by NF5 as well as NF5 without special support to perform this procedure. This can also be achieved through a mechanism of subscribe-notify type for appropriate procedures. For example, NF2 and NF5 can subscribe to "UE Location Change Reporting" from NF1. NF1 maintains subscription info., And can notify NF2 and NF5 individually when UE location change occurs. In the future, NF6 can join the same procedure, and NF1 may not need special support.

<Functional description>

The proposed interconnection model can introduce IRF. IRF can be proposed as a 3GPP-defined network function. This section can provide a functional description of IRF and other related aspects.

The function of the IRF according to one embodiment is as follows.

The IRF stores the binding between the identity of the UE and the interface layer identity (e.g., the instance number) of each serving NF having an active session to the UE. For non-UE association signaling, any identifier that allows the NF to locate the non-UE associated signaling session may be used as the key value for the binding network function. In the case of an NF that does not interface directly with the IRF (eg, a roaming scenario), the IRF may store the identity of the IRF of the remote-PLMN that the NF can reach.

The IRF can update the binding repository if the identity of the serving NF is changed for a given UE. Updates may occur, for example, due to UE mobility, load re-balancing (e.g., scale-in or scale-out of the VM) or restoration reasons.

The IRF can examine the message header to determine the identity of the session and the destination NF. In the case of a given binding-key identity, the IRF may look up the internal binding repository to determine the identity of the interface layer identity (e.g., instance number) or remote IRF of the destination NF. If there is no binding, the IRF is based on the appropriate instance of the NF (e.g., based on load / overload information) or a remote IRF (e.g., based on PLMN information in the logical identity of the destination NF) ), And update the corresponding local repository with the binding. IRF can route messages accordingly.

The IRF can optionally perform message acknowledgment according to the operator's configuration. For example, if the configuration of the operator prohibits NF1 from invoking a specific message (e.g., "Change APN-AMBR of UE") in the NF4 direction, the IRF may reject the corresponding message. The IRF can selectively protect the NF during a signaling storm by performing an overload control. For example, overload control may include pacing of messages sent to a given NF based on load / overload conditions.

The protocol between each NF and IRF can be defined as stage 3 (stage 3). If another protocol is defined, the IRF may need to perform a protocol conversion while routing the message between the two NFs.

To perform message authentication, the IRF may check the "message type", "source NF" and "destination NF" parameters in the message header and allow or deny the message based on the local configuration.

3 illustrates a binding storage of an IRF according to one embodiment.

Referring to FIG. 3, an exemplary binding storage of an IRF is illustrated in the case of assuming network functions NF1 to NF5 in the network according to an embodiment.

An "instance number" can be used to indicate an "interface layer association" between the IRF and NF for a given UE session. However, other identities / formats that reflect this can also be used.

The binding-key identity of the UE-associated signaling session may be anything that allows the NF to uniquely locate the UE's session while processing the received message. For example, there may be an International Mobile Subscriber Identity (IMSI), an Internet Protocol (IP) address, and the like.

The binding key identity of the non-UE associated signaling session may be anything that allows the NF to uniquely locate the associated non-UE associated signaling session while processing the received message. For example, there may be a global RAN ID signaling session dedicated to a particular RAN.

4 is a diagram illustrating a communication method of routing messages between NF1 and NF4 according to an exemplary embodiment of the present invention.

Referring to Figure 4, a communication method performed by a processor of an IRF routing a message between NF1 and NF4 in a non-roaming case according to one embodiment is shown. Here, NF1 represents the source network function, and NF4 represents the destination network function.

In step 410, if the session of the UE or the non-UE associated session is not present in NF4 (e.g., this message includes a new session in NF4 as part of the attach or relocation types of the procedure) , NF1 can select NF4 taking into account the appropriate parameters and derive the logical identity of NF4. If the UE's session or non-UE associated session already exists in NF4, NF1 may simply send the message to NF4 using a logical identity (e.g., Fully Qualified Domain Name (FQDN)).

In step 420, NF1 may include a binding key identity (e.g., the identity of the UE) and an identifier of the "destination NF " (e.g., logical identity of NF4) in the message header and may send the message to the IRF. Information related to the IRF can be provided locally to the NFs.

In step 430, if the identifier of the destination NF (e.g., the logical identity of NF4) points to NF4 in the local-PLMN, the IRF associates the binding key identity (e.g., UE identity) with the NF4's interface layer identity NF4). &Lt; / RTI &gt;

At step 440, if no binding is present (e.g., the first message for the UE's session to NF4), the IRF selects the appropriate instance of NF4 based on the load / To the appropriate instance of the selected NF4. In addition, the IRF may update the local repository (e.g., the internal repository) using a binding between the binding key identity (e.g., the identity of the UE) and the instance number of the NF.

If at step 430 a binding is present or at step 440 an appropriate instance of NF4 is selected, at step 450 the IRF may send the message to the appropriate instance of NF4.

According to one embodiment, each NF may periodically transmit an active set list of instances with the load / overload information to the IRF.

In step 460, until the UE's session or non-UE associated session maintains an active state, the IRF sends an identifier of the NF4 (e.g., NF4 in the Local-PLMN) to the binding key identity &Lt; / RTI &gt; the instance number of &lt; / RTI &gt; This binding allows the IRF to route any message to the UE's session or NF4 for a non-UE associated session.

5 is a diagram illustrating a communication method of routing a message between NF1 and NF4 according to another embodiment.

Referring to FIG. 5, there is shown a communication method performed by a processor of an IRF routing a message between NF1 and NF4 in a roaming case according to an embodiment. Here, NF1 represents the source network function, and NF4 represents the destination network function.

In step 510, if the UE's session or non-UE associated session is not present in NF4 (e.g., this message includes a new session in NF4 as part of the attach or relocation types of the procedure) , NF1 can select NF4 taking into account the appropriate parameters and derive the logical identity of NF4. If the UE's session or non-UE associated session already exists in NF4, NF1 may simply send the message to NF4 using a logical identity (e.g., Fully Qualified Domain Name (FQDN)).

At step 520, NF1 may include a binding key identity (e.g., the identity of the UE) and an identifier of the "destination NF " (e.g., a logical identity of NF4) in the message header and may send the message to the IRF. Information related to the IRF can be provided locally to the NFs.

At step 530, upon receipt of the message, the IRF may examine the message header to derive a binding key identity (e.g., identity of the UE) and an identifier of the destination NF (e.g., the logical identity of NF4). If the identifier of the destination NF (e.g., the logical identity of NF4) indicates NF4 in the remote-PLMN, the IRF may derive the identity of the IRF in the target-PLMN (e.g., remote-PLMN). For example, the IRF may derive the identity of the IRF in the target-PLMN based on local configuration or DNS based resolution. The IRF may update the internal binding to point to the IRF of the remote-PLMN for NF4.

In step 540, the IRF may send the message to the IRF of the remote-PLMN.

At step 550, the IRF of the remote-PLMN may look up an internal repository for binding between the binding key (e.g., the UE's identity) and the interface layer identity of the NF4 (e.g., the instance number of NF4). Here, the internal repository may be included in the IRF of the remote-PLMN.

At step 560, the IRF of the remote-PLMN may send the message to the appropriate instance of NF4.

In step 570, until the session of the UE or the non-UE associated session remains active, the IRF sends an identifier of the NF4 (e.g., an identifier of the IRF in the remote-PLMN) and a binding key identity Lt; / RTI &gt; This binding allows the IRF to route any message to the UE's session or NF4 for a non-UE associated session.

6 is a diagram illustrating an NF binding management method of an IRF according to an exemplary embodiment of the present invention.

Referring to FIG. 6, a method of managing a binding between a UE session or a non-UE associated session and a corresponding serving NF in an IRF for UE-associated signaling or non-UE-associated signaling according to an embodiment is illustrated.

When a UE session or a non-UE associated session is created in the NF (e.g., during a connection, a procedure such as establishing a new PDU session, relocating, etc.) according to one embodiment, the NF may select "Add UE binding" Quot; Add non-UE binding "message. &Lt; / RTI &gt; The IRF may create a new binding in the binding store (e.g., internal store, local store, etc.).

To update the existing binding, the NF may send an "Update UE binding" message to the IRF. Thus, the IRF can update the binding store. Because of the scale-in, scale-out, or restore function, this can occur if the NF changes the instance for an existing UE's session.

When the session of an existing UE is released by the NF (e.g., during a relocation or PDU session release procedure), the NF may send a "Remove UE binding" message to the IRF. The IRF may clear the binding store for the UE's session.

The above message can be sent independently or by piggybacking other related messages. For example, while sending a "PDU session establishment" message to NF2, NF1 sends an "Add UE binding" to create a binding between the UE's session and the serving instance of NF1 in the IRF May piggyback a message "Add non-UE binding &quot;.

The embodiments described above may be implemented in hardware components, software components, and / or a combination of hardware components and software components. For example, the devices, methods, and components described in the embodiments may be implemented within a computer system, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, such as an array, a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

The components described in the embodiments may be implemented by a programmable logic device such as one or more DSP (Digital Signal Processor), a processor, a controller, an application specific integrated circuit (ASIC), and a field programmable gate array Logic Element, other electronic devices, and combinations thereof. &Lt; RTI ID = 0.0 &gt; At least some of the functions or processes described in the embodiments may be implemented by software, and the software may be recorded in a recording medium. The components, functions and processes described in the embodiments may be implemented by a combination of hardware and software.

Although the embodiments have been described with reference to the drawings, various technical modifications and variations may be applied to those skilled in the art. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI &gt; or equivalents, even if it is replaced or replaced.

Claims (1)

A communication method of an IRF for performing communication with a source network function (source NF) and a destination network function (destination NF)
Receiving a message from the source network function, the message including a binding key and an identifier of the destination network function;
Determining whether the destination network function is in a local-PLMN corresponding to the IRF based on an identifier of the destination network function;
Looking up a binding between the binding key and an interface layer identity of the destination network function in an internal repository of the IRF if the destination network function is present in the local-PLMN; And
Transmitting the message to the destination network function using the binding if the binding exists in the internal repository
/ RTI &gt;

Images