Enabling direct service-based requests from radio access network node to 5G core network functions
By introducing a direct signaling mechanism between the 5G core network and the radio access network, the cumbersome signaling process in the prior art is solved, direct communication between RAN and 5GC NF is realized, and network performance and efficiency are improved.
Patent Information
- Application Number
- CN202280093748.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-17
- Publication Date
- 2024-11-01
AI Technical Summary
The communication between the existing 5G core network and the radio access network has the problem of being difficult to achieve direct service requests, which leads to cumbersome signaling process and affects network performance.
By introducing a direct signaling mechanism between RAN and 5GC, RAN nodes can directly address and discover 5GC NFs that handle UE context or PDU sessions, and extend signaling on the N2 interface to optimize service request and handover processes.
Direct communication between RAN and 5GC NF is realized, frequent signaling processes are optimized, especially during service requests and Xn-based handover, improving network performance and efficiency.
Smart Images

Figure CN118891925A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to a method, apparatus, system and computer program, and in particular but not exclusively to enabling direct service-based requests from a radio access network node to a 5G core network function. Background Art
[0002] A communication system can be viewed as a facility for enabling communication sessions between two or more entities such as user terminals, base stations and / or other nodes by providing carrier waves between the various entities involved in the communication path. For example, a communication system can be provided by a communication network and one or more compatible communication devices. A communication session may include, for example, data communications for carrying communications such as voice, video, electronic mail (email), text messages, multimedia and / or content data. Non-limiting examples of the services provided include two-way or multi-way calls, data communications or multimedia services, and access to data network systems such as the Internet.
[0003] In a wireless communication system, at least a portion of a communication session between at least two stations occurs over a wireless link. Examples of wireless systems include public land mobile networks (PLMNs), satellite-based communication systems, and different wireless local area networks such as wireless local area networks (WLANs). Some wireless systems may be divided into cells and are therefore often referred to as cellular systems.
[0004] A user can access the communication system through an appropriate communication device or terminal. The user's communication device may be referred to as a user equipment (UE) or user device. The communication device is provided with appropriate signal receiving and sending means to achieve communication, such as access to a communication network or direct communication with other users. The communication device can access a carrier provided by a site (e.g., a base station of a cell) and send and / or receive communications on the carrier.
[0005] A communication system and associated equipment typically operate according to a given standard or specification that states what the various entities associated with the system are allowed to do and how it should be achieved. Communication protocols and / or parameters for the connection are also typically defined. An example of a communication system is UTRAN (3G radio). Other examples of communication systems are the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology and the so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP). Summary of the invention
[0006] According to one aspect, an apparatus, a network node or an entity is provided, comprising components for: obtaining an information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with a network function; and providing the network function identifier to an access node, the access node being associated with the user equipment identifier and / or with a session matching the network function context identifier.
[0007] The network function identifier may enable the access node to directly access the network function associated with the network function identifier.
[0008] The apparatus or entity may further include means for providing a session identifier to the access node.
[0009] The network function identifier may include at least one of: a network address of a network function associated with the network function identifier; and an identifier of a network function set including the network function associated with the network function identifier.
[0010] The means for obtaining the information element may be for receiving the information element from a network function associated with the network function identifier.
[0011] The means for receiving the information element from the network function associated with the network function identifier may be configured to receive the information element within an N2 interface message container.
[0012] The information element may also include a session identifier.
[0013] The information element may also include binding information.
[0014] The component for providing information elements to an access node can be used to generate and provide at least one of the following items: an interface protocol data unit session request, which includes information elements from the access and mobility function node to the access node; and a discovery response, which includes information elements from the access and mobility function node to the access node.
[0015] The component for obtaining the information element may also be used to receive a network function context identifier, a network function identifier, and a session identifier in a Nsmf_PDUSession_CreateSMContext response, and the component may also be used to store the information element in a context associated with the identified session.
[0016] The means for providing the network function identifier may also be used to include a network function context identifier; and a network function identifier in an N2 PDU session request when receiving a Namf_Communication_N1N2Message transfer message.
[0017] The component may also be configured to receive a Namf_Communication_N1N2Message transfer request including a session identifier, and in response to receiving the Namf_Communication_N1N2Message transfer request, provide a network function identifier to an access node associated with a session identified by the session identifier.
[0018] The means for obtaining the information element may further be for: receiving a user equipment identifier associated with the first user equipment and the network function identifier; and storing the user equipment identifier associated with the first user equipment and the network function identifier in a context associated with the identified first user equipment.
[0019] The component may also be configured to provide a second user equipment identifier associated with the first user equipment to a network function associated with the network function identifier.
[0020] The user equipment identifier may be a first user equipment identifier, and the component may also be used to receive a discovery request user equipment identifier from an access node, wherein the discovery request may include at least one of the following items: a second user equipment identifier; a session identifier; and a type of network function to be discovered that is associated with the network function identifier.
[0021] The network nodes may include access and mobility function nodes.
[0022] The network function associated with the network function identifier may include a session management function.
[0023] According to a second aspect, there is provided an apparatus, access node or entity comprising means for: receiving an information element comprising: a network function identifier associated with a network function; and employing the information element to directly access the network function associated with the network function identifier.
[0024] The network function identifier may include at least one of: a network address of the network function; and an identifier of a set of network functions including the network function.
[0025] The information element may further include a network function context identification; and the means for directly accessing the network function associated with the network function identifier using the information element may further be configured to: provide the network function context identifier in the request for the network function.
[0026] This component can also be used to store information elements.
[0027] The component may also be configured to forward the information element to the target access node as part of a user equipment context transfer.
[0028] The means for receiving the information element may be configured to receive the information element from the second network function.
[0029] The component for receiving the information element from the second network function can be used to receive the information element according to one of the following items: an interface protocol data unit session request, the interface protocol data unit session request includes the information element from the access and mobility function; the user equipment context transfer, the user equipment context transfer includes the information element from the source access node; and the discovery response, the discovery response includes the information element from the access and mobility function node.
[0030] The component may also be configured to request discovery of network functions from the second network function, wherein the request for discovery may include at least one of: a user device identifier; a session identifier; and a type of network function to be discovered.
[0031] The information element may also include a session identifier.
[0032] The information element may also include binding information.
[0033] A component for using an information element to directly access a network function associated with a network function address / identifier / set identifier can be used for the following items: generating a discovery message including a network set identifier and obtaining a response indicating direct communication with the network function; and generating a request to communicate directly with the indicated network function.
[0034] According to a third aspect, a device, a session management function or an entity is provided, comprising components for: sending a session management container in a Namf_Communication_N1N2Messge transmission request, wherein the session management container includes: an identifier of the session, an identifier of the session management function, and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request includes an identifier of the session management context.
[0035] The identifier of the session management function may include at least one of: a network address of the session management function, and an identifier of a set of session management functions that includes the session management function.
[0036] According to a fourth aspect, a method for a network node or entity is provided, the method comprising: obtaining an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function identifier; and providing the network function identifier to an access node, the access node being associated with the user equipment identifier and / or with a session matching the network function context identifier.
[0037] The network function identifier may enable the access node to directly access the network function associated with the network function identifier.
[0038] The method may also include providing a session identifier to the access node.
[0039] The network function identifier may include at least one of: a network address of a network function associated with the network function identifier; and an identifier of a network function set including the network function associated with the network function identifier.
[0040] Obtaining the information element may include receiving the information element from a network function associated with the network function identifier.
[0041] Receiving the information element from the network function associated with the network function identifier may include receiving the information element within an N2 interface message container.
[0042] The information element may also include a session identifier.
[0043] The information element may also include binding information.
[0044] Providing information elements to the access node may include generating and providing at least one of: an interface protocol data unit session request, the interface protocol data unit session request including information elements from the access and mobility function node to the access node; and a discovery response, the discovery response including information elements from the access and mobility function node to the access node.
[0045] Obtaining the information element may further include receiving a network function context identifier, a network function identifier, and a session identifier in a Nsmf_PDUSession_CreateSMContext response, and the method may further include storing the information element in a context associated with the identified session.
[0046] Providing the network function identifier may also include: including a network function context identifier; and the network function identifier in an N2PDU session request when receiving a Namf_Communication_N1N2Message transfer message.
[0047] The method may further include receiving a Namf_Communication_N1N2Message transfer request including a session identifier, and in response to receiving the Namf_Communication_N1N2Message transfer request, providing a network function identifier to an access node associated with the session identified by the session identifier.
[0048] Obtaining the information element may also include: receiving a user equipment identifier, the user equipment identifier associated with the first user equipment and the network function identifier; and storing the user equipment identifier associated with the first user equipment and the network function identifier in a context associated with the identified first user equipment.
[0049] The method may further include providing a second user equipment identifier associated with the first user equipment to a network function associated with the network function identifier.
[0050] The user equipment identifier may be a first user equipment identifier, and the method may further include receiving a discovery request user equipment identifier from an access node, wherein the discovery request may include at least one of: a second user equipment identifier; a session identifier; and a type of network function associated with the network function identifier to be discovered.
[0051] The network nodes may include access and mobility function nodes.
[0052] The network function associated with the network function identifier may include a session management function.
[0053] According to a fifth aspect, there is provided a method for accessing a node or entity, the method comprising: receiving an information element, the information element comprising: a network function identifier; and using the information element to directly access a network function associated with the network function identifier.
[0054] The network function identifier may include at least one of: a network address of the network function; and an identifier of a set of network functions including the network function.
[0055] The information element may further include a network function context identification; and employing the information element to directly access a network function associated with the network function identifier may further include providing the network function context identifier in the request for the network function.
[0056] The method may further include storing the information element.
[0057] The method may also include forwarding the information element to the target access node as part of a user equipment context transfer.
[0058] Receiving the information element may include receiving the information element from the second network function.
[0059] Receiving the information element from the second network function may include receiving the information element according to one of: an interface protocol data unit session request, the interface protocol data unit session request including the information element from the access and mobility function; a user equipment context transfer, the user equipment context transfer including the information element from the source access node; and a discovery response, the discovery response including the information element from the access and mobility function node.
[0060] The method may further include requesting discovery of network functions from the second network function, wherein the request for discovery may include at least one of: a user equipment identifier; a session identifier; and a type of network function to be discovered.
[0061] The information element may also include a session identifier.
[0062] The information element may also include binding information.
[0063] Directly accessing a network function associated with a network function address / identifier / set identifier using an information element may include: generating a discovery message including a network set identifier and obtaining a response indicating direct communication with the network function; and generating a request for direct communication with the indicated network function.
[0064] According to a sixth aspect, a method for a session management function or entity is provided, the method comprising: sending a session management container in a Namf_Communication_N1N2Messge transmission request, wherein the session management container comprises: an identifier of the session, an identifier of the session management function, and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises an identifier of the session management context.
[0065] The identifier of the session management function may include at least one of: a network address of the session management function, and an identifier of a set of session management functions that includes the session management function.
[0066] According to a seventh aspect, there is provided an apparatus, a network node or an entity, comprising: at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to perform at least the following items: obtain an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function identifier; and provide the network function identifier to an access node, the access node being associated with the user equipment identifier and / or with a session matching the network function context identifier.
[0067] The network function identifier may enable the access node to directly access the network function associated with the network function identifier.
[0068] The apparatus or entity may also be caused to provide a session identifier to the access node.
[0069] The network function identifier may include at least one of: a network address of a network function associated with the network function identifier; and an identifier of a network function set including the network function associated with the network function identifier.
[0070] The means caused to obtain the information element may be caused to receive the information element from a network function associated with the network function identifier.
[0071] The means caused to receive the information element from the network function associated with the network function identifier may be caused to receive the information element within an N2 interface message container.
[0072] The information element may also include a session identifier.
[0073] The information element may also include binding information.
[0074] The device that is caused to provide information elements to the access node may be caused to generate and provide at least one of the following items: an interface protocol data unit session request, the interface protocol data unit session request includes information elements from the access and mobility function node to the access node; and a discovery response, the discovery response includes information elements from the access and mobility function node to the access node.
[0075] The device caused to obtain the information element may also be caused to receive a network function context identifier, a network function identifier, and a session identifier in a Nsmf_PDUSession_CreateSMContext response, and the device may also be caused to store the information element in a context associated with the identified session.
[0076] The means caused to provide the network function identifier may further be caused to: include the network function context identifier; and the network function identifier in the N2 PDU session request when receiving the Namf_Communication_N1N2Message transfer message.
[0077] The apparatus may also be caused to perform the following: receiving a Namf_Communication_N1N2Message transfer request including a session identifier, and in response to receiving the Namf_Communication_N1N2Message transfer request, providing a network function identifier to an access node associated with a session identified by the session identifier.
[0078] The apparatus caused to obtain the information element may also be caused to perform the following items: receiving a user equipment identifier, the user equipment identifier being associated with the first user equipment and the network function identifier; and storing the user equipment identifier associated with the first user equipment and the network function identifier in a context associated with the identified first user equipment.
[0079] The apparatus may also be caused to provide a second user equipment identifier associated with the first user equipment to a network function associated with the network function identifier.
[0080] The user equipment identifier may be a first user equipment identifier and may also enable the apparatus to receive a discovery request user equipment identifier from an access node, wherein the discovery request may include at least one of: a second user equipment identifier; a session identifier; and a type of network function associated with the network function identifier to be discovered.
[0081] The network nodes may include access and mobility function nodes.
[0082] The network function associated with the network function identifier may include a session management function.
[0083] According to an eighth aspect, there is provided a device, an access node or an entity, comprising: at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, so that the device performs at least the following items: receiving an information element, the information element comprising: a network function identifier; and using the information element to directly access a network function associated with the network function identifier.
[0084] The network function identifier may include at least one of: a network address of the network function; and an identifier of a set of network functions including the network function.
[0085] The information element may further include a network function context identification; and the apparatus caused to employ the information element to directly access a network function associated with the network function identifier may further be caused to provide the network function context identifier in the request for the network function.
[0086] The apparatus may also be caused to store the information element.
[0087] The apparatus may also be caused to forward the information element to the target access node as part of a user equipment context transfer.
[0088] The means for receiving the information element may be caused to receive the information element from the second network function.
[0089] The apparatus enabled to receive the information element from the second network function may be enabled to receive the information element according to one of: an interface protocol data unit session request, the interface protocol data unit session request including the information element from the access and mobility function; a user equipment context transfer, the user equipment context transfer including the information element from the source access node; and a discovery response, the discovery response including the information element from the access and mobility function node.
[0090] The apparatus may also be caused to request discovery of network functions from the second network function, wherein the request for discovery may include at least one of: a user equipment identifier; a session identifier; and a type of network function to be discovered.
[0091] The information element may also include a session identifier.
[0092] The information element may also include binding information.
[0093] A device that is enabled to employ an information element to directly access a network function associated with a network function address / identifier / set identifier may be enabled to perform the following: generate a discovery message including a network set identifier and obtain a response indicating direct communication with the network function; and generate a request to communicate directly with the indicated network function.
[0094] According to a ninth aspect, a device, a session management function or an entity is provided, comprising: at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the device to perform at least the following items: sending a session management container in a Namf_Communication_N1N2Messge transmission request, wherein the session management container comprises: an identifier of the session, an identifier of the session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises an identifier of the session management context.
[0095] The identifier of the session management function may include at least one of: a network address of the session management function and an identifier of a set of session management functions including the session management function.
[0096] According to the tenth aspect, a device, a network node or an entity is provided, comprising: a component for obtaining an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function identifier; and a component for providing the network function identifier to an access node, the access node being associated with the user equipment identifier and / or with a session matching the network function context identifier.
[0097] According to an eleventh aspect, there is provided an apparatus, an access node or an entity comprising: a component for receiving an information element, the information element comprising: a network function identifier; and a component for employing the information element to directly access a network function associated with the network function identifier.
[0098] According to the twelfth aspect, a device, a session management function or an entity is provided, comprising: a component for sending a session management container in a Namf_Communication_N1N2Messge transmission request, wherein the session management container includes an identifier of the session, an identifier of the session management function and an identifier of a session management context associated with the session; and a component for receiving a request related to the session from an access node, wherein the request includes an identifier of the session management context.
[0099] According to a thirteenth aspect, a computer program is provided, the computer program comprising a computer program [or a computer-readable medium comprising program instructions] comprising instructions for causing an apparatus, a network node or an entity to perform at least the following items: obtaining an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function identifier; and providing the network function identifier to an access node, the access node being associated with the user equipment identifier and / or with a session matching the network function context identifier.
[0100] According to a fourteenth aspect, a computer program is provided, comprising a computer program [or a computer-readable medium comprising program instructions] for causing a device, an access node or an entity to perform at least the following items: receiving an information element, the information element comprising: a network function identifier associated with a network function; and using the information element to directly access the network function associated with the network function identifier.
[0101] According to the fifteenth aspect, a computer program is provided, comprising a computer program [or a computer-readable medium comprising program instructions] comprising instructions for causing a device, a session management function or an entity to perform at least the following items: sending a session management container in a Namf_Communication_N1N2Messge transmission request, wherein the session management container comprises: an identifier of the session, an identifier of the session management function, and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises an identifier of the session management context.
[0102] According to a sixteenth aspect, there is provided a non-transitory computer-readable medium, comprising program instructions for causing a device, a network node, or an entity to at least perform the following: obtain an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function identifier; and provide the network function identifier to an access node, the access node being associated with the user equipment identifier and / or with a session matching the network function context identifier. According to a seventeenth aspect, there is provided a non-transitory computer-readable medium, comprising program instructions for causing a device, an access node, or an entity to at least perform the following: receive an information element, the information element comprising: a network function identifier associated with a network function; and use the information element to directly access the network function associated with the network function identifier.
[0103] According to the eighteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing a device, a session management function or an entity to perform at least the following items: sending a session management container in a Namf_Communication_N1N2Messge transmission request, wherein the session management container comprises an identifier of the session, an identifier of the session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises an identifier of the session management context.
[0104] According to the nineteenth aspect, a device, a network node or an entity is provided, comprising: obtaining a circuit system configured to obtain an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function identifier; and providing a circuit system configured to provide the network function identifier to an access node, the access node being associated with the user equipment identifier and / or with a session matching the network function context identifier.
[0105] According to the twentieth aspect, there is provided a device, an access node or an entity, comprising: a receiving circuit system configured to receive an information element, the information element comprising: a network function identifier associated with the network function; and an adopting circuit system configured to adopt the information element to directly access the network function associated with the network function identifier.
[0106] According to the twenty-first aspect, a device, a session management function or an entity is provided, comprising: a sending circuit system, configured to send a session management container in a Namf_Communication_N1N2Messge transmission request, wherein the session management container includes an identifier of the session, an identifier of the session management function, and an identifier of a session management context associated with the session; and a receiving circuit system, configured to receive a request related to the session from an access node, wherein the request includes an identifier of the session management context.
[0107] According to the twenty-second aspect, a computer-readable medium is provided, comprising program instructions for causing an apparatus, a network node or an entity to perform at least the following items: obtaining an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function identifier; and providing the network function identifier to an access node, the access node being associated with the user equipment identifier and / or with a session matching the network function context identifier.
[0108] According to the twenty-third aspect, a computer-readable medium is provided, comprising program instructions for causing a device, an access node or an entity to perform at least the following items: receiving an information element, the information element comprising: a network function identifier associated with a network function; and using the information element to directly access the network function associated with the network function identifier.
[0109] According to the twenty-fourth aspect, a computer-readable medium is provided, comprising program instructions for causing a device, a session management function or an entity to perform at least the following items: sending a session management container in a Namf_Communication_N1N2Messge transmission request, wherein the session management container includes an identifier of the session, an identifier of the session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request includes an identifier of the session management context.
[0110] An apparatus comprises means for performing the actions of the method as described above.
[0111] A device is configured to perform the actions of the method described above.
[0112] A computer program includes program instructions for causing a computer to execute the above method.
[0113] A computer program product, stored on a medium, can cause an apparatus to execute the method described herein.
[0114] According to one aspect, a non-transitory computer-readable medium including program instructions is provided, the program instructions being used to cause an apparatus to at least perform a method according to any one of the preceding aspects.
[0115] In the above, many different embodiments are described. It should be understood that further embodiments can be provided by combining any two or more of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0116] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:
[0117] Figure 1 shows a representation of a network system according to some example embodiments;
[0118] Figure 2 shows a representation of a control device according to some example embodiments;
[0119] Figure 3 shows representations of apparatus according to some example embodiments;
[0120] Figure 4 and Figure 5 shows a flow chart of N2 service management signaling according to an example embodiment;
[0121] Figure 6 A flow chart illustrating an Xn-based handoff with a direct request to a service management function according to some example embodiments; and
[0122] Figure 7 A flow chart is shown for implementing direct service-based request signaling for 5G core network functions according to some exemplary embodiments. DETAILED DESCRIPTION
[0123] In the following, certain embodiments are explained with reference to a mobile communication device capable of communicating via a wireless cellular system and a mobile communication system serving such a mobile communication device. Figure 1 , Figure 2 and Figure 3 Certain general principles of wireless communication systems, their access systems and mobile communication devices are briefly explained to help understanding the technology underlying the described examples.
[0124] Figure 1 A schematic diagram of a 5G system (5GS) is shown. The 5GS may include a terminal or user equipment (UE), a 5G radio access network (5GRAN) or a next generation radio access network (NG-RAN), a 5G core network (5GC), one or more application functions (AFs), and one or more data networks (DNs).
[0125] The 5G-RAN may include one or more gNodeBs (GNBs), one or more gNodeB (GNB) distributed unit functions connected to one or more gNodeB (GNB) centralized unit functions, or one or more next generation eNodeBs (NGENBs).
[0126] 5GC may include, for example, the following entities: network slice selection function (NSSF); network exposure function (NEF); network repository function (NRF); policy control function (PCF); unified data management (UDM); application function (AF); authentication server function (AUSF); access and mobility management function (AMF); and session management function (SMF).
[0127] Access to 5GC can more generally be accomplished via a 5G access network (3G-AN), which can correspond to 3GPP access (e.g., NR or LTE access with 5G-RAN) or non-3GPP access (e.g., untrusted WLAN access via N3IWF, trusted WLAN access via TNGF, wired access via W-AGF).
[0128] Figure 2 Shows the control Figure 1 An example of a control device 200 for the functions of a 5GRAN or 5GC shown. The control device may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. At least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may, for example, allow one or more steps to be executed to perform one or more aspects of the present aspect. The software code 215 may be stored in the ROM 211b. The control device 200 may be interconnected with another control device 200 that controls another function of the 5GRAN or 5GC. In some embodiments, each function of the 5GRAN or 5GC includes a control device 200. In an alternative embodiment, two or more functions of the 5GRAN or 5GC may share a control device.
[0129] Figure 3 An example of a terminal 300 is shown, such as Figure 1The terminal shown. The terminal 300 can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include user equipment, a mobile station (MS) or a mobile device such as a mobile phone or a so-called "smart phone", a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or tablet computer equipped with wireless communication capabilities, a machine type communication (MTC) device, an Internet of Things (IoT) type communication device, or any combination of these devices. The terminal 300 can provide data communications, such as for bearer communications. The communication can be one or more of voice, email (email), text message, multimedia, data, machine data, etc.
[0130] The terminal 300 may receive signals over the air or radio interface 307 via suitable means for receiving, and may transmit signals via suitable means for transmitting radio signals. Figure 3 In the mobile device, the transceiver arrangement is schematically represented by a block 306. The transceiver arrangement 306 may be provided, for example, by a radio part and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.
[0131] The terminal 300 may be equipped with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for software and hardware assisted execution of the tasks designed to be performed, including controlling access to and communication with access systems and other communication devices. The at least one processor 301 is coupled to the RAM 311a and the ROM 311b. The at least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may, for example, allow the execution of one or more aspects of the present invention. The software code 308 may be stored in the ROM 311b.
[0132] The processor, memory and other associated control means may be provided on an appropriate circuit board and / or in a chipset. This feature is indicated by reference numeral 304. The device may optionally have a user interface, such as a keyboard 305, a touch-sensitive screen or keyboard, a combination thereof, etc. Depending on the type of device, one or more of a display, a speaker and a microphone may optionally be provided.
[0133] In such Figure 1 In the 5GC architecture shown and specified in 3GPP TS23.501, AMF (Access and Mobility Management Function) is located between 5GC (5G Core) and RAN (Radio Access Network). For 5GC, AMF is configured to present an HTTP-based interface based on granular services and can also adopt services provided by other core network functions (NFs).
[0134] However, for the RAN, the AMF is configured to adopt a non-service based interface, such as the N2 interface between the AMF and the RAN.
[0135] All communications between the RAN and 5GC pass through the AMF. For security reasons, the AMF is configured to hide the permanent UE identifier (Subscriber Permanent Identifier - SUPI) used in the 5GC from the RAN nodes and instead allocate a temporary and changeable identifier, which may be designated as the AMF UE Next Generation Access Protocol (NGAP) ID, for identifying UEs communicating with RAN nodes over the NG interface.
[0136] For example, 3GPP TS23.502 and the related figures in the document show examples such as PDU session establishment, where the AMF / NAS handler is aware of the PDU sessions and the SMF that serves them. In addition, the document shows an Xn-based handover, where only N2 signaling can bypass the NAS processor. In an N2-based handover, the NAS processor can be completely bypassed because no NAS signaling is involved. In addition, during the service request process, the AMF / NAS handler is aware of the PDU sessions and the SMF that serves them.
[0137] It can also be considered desirable to allow the introduction of service-based architecture communications directly between the RAN and the 5GC. For example, in some cases, such as during a path switch request in a handover procedure, the AMF acts only as a forwarding node for messages from the RAN node to the SMF during the handover procedure. As an example, the purpose of the Namf_Communication_N2InfoNotify service operation in TS23.502 is to notify the CN NFs that have subscribed to the specific information of specific N2 message information. The purpose of the Namf_Communication_N1MessageNotify service operation in TS23.502 (usually subscribed by the SMF) is to notify the destination CN NF of the N1 message received from the UE.
[0138] The concepts discussed in the embodiments of this document are intended to enable RAN nodes to directly address services that may be provided by NFs in 5GC. Such a concept may be one where a RAN node is able to discover a 5GC NF that handles a UE context or PDU session, and a 5GC NF that is configured to understand the RAN specific PDU identity provided.
[0139] Furthermore, in some embodiments, the RAN node is configured to be able to discover the MB-SMF handling a particular MBS session and communicate directly with the associated MB-SMF.
[0140] Currently, if the AMF receives an event subscription, the AMF is configured to send the event subscription to the RAN node, which is then configured to send the event notification directly to the core node. In some cases, the SMF is known to add the event subscription information to the N2 container which is transparently forwarded by the AMF.
[0141] As described above, embodiments enable direct signaling between the RAN and 5GC NF to optimize processes with frequent signaling. Examples of such frequent signaling are service requests and Xn-based handover processes, and are discussed in further detail below, but it should be understood that the methods and functions discussed below can be applied to other processes without substantial creative input.
[0142] For example, in some embodiments, and described in further detail in the following examples, a solution for N2SM related signaling is provided (which also applies to path switch requests occurring during X2 handovers). These embodiments describe extending the signaling from the AMF to the AN (access network) node associated with the PDU session with the SMF ID / address / set ID, possible binding information for the SMF handling the PDU session, and the S-context ID associated with the PDU session in order to discover the SMF handling the PDU session. The AMF can then also be configured to provide the SM context ID, SMF ID / address / set ID, and possible binding information for a given UE and PDU session received in previous signaling received from the SMF.
[0143] In some embodiments, the SMF is configured to use the existing Namf_Communication_N1N2 message to transmit AMF services (or Nsmf_CreateSM context response or Nsmf_Update SM context response), and provide the SM context ID, SMF set ID, and / or SMF instance ID, and / or SMF URI / SMF address as defined for the above-mentioned existing services in the encapsulated N2SM information, and the AMF is configured to transparently forward the N2 SM information to the AN node.
[0144] In addition, in some embodiments, the AN node is configured to employ the received SMF ID / address / set ID, SM context ID and / or information derived from the received binding information to address subsequent PDU session-related service (SB)-based session management (SM) requests directly to a given SMF for that particular UE and PDU session, and also includes an SM context ID identifying the SM context in the SMF (which in particular identifies the UE).
[0145] In some embodiments, the network may be configured for PDU session-related signaling (and also for non-PDU session-related signaling), the AN node being configured to query the AMF for the core network function (NF) serving the UE and / or PDU session, and use the received information about the core NF to address subsequent requests for UE context-based or PDU session-related services directly to that specific core NF.
[0146] In order to discover the SMF handling the PDU session, the signaling from the AMF to the AN node related to the PDU session is extended with information such as the SMF ID / address / set ID, possible binding information for the SMF handling the PDU session, and the SM context ID related to the PDU session (e.g., the URI of the SM context resource in the SMF).
[0147] For example, the N2_PDU_Session_Request_Message associated with the NGAP PDU Session Resource Setup Request message may be extended as follows: Figure 4 as shown in the example.
[0148] In such an embodiment, the AMF may be configured to provide the SM context ID, SMF ID / address / aggregation ID, and binding information received in previous signaling received from the SMF.
[0149] In some embodiments, the AMF may also include an identifier that may identify a given UE-N2SMAP_SM_UE ID. This identifier may help the SMF locate the context of the UE based on the message. For example, as received in the Nsmf_PDUSession_CreateSMContext response.
[0150] The AN node may also be configured to store and use the received SMF ID / address / aggregation ID, information derived from the received binding information and / or the SM context ID to address subsequent PDU session related requests directly to the SMF.
[0151] For example, in some embodiments, the AN node can use this information to query the NRF for the configuration file of the SMF. In addition, in some embodiments, the AN node can be configured to delegate SMF discovery to the SCP and provide this information as a discovery parameter to the SCP. In some embodiments, the AN node is configured to route N2 SM signaling based on the received binding information (SMF ID / address / collection ID), and it includes binding information equivalent to the binding information received in the request to the SMF for a given UE and PDU session. In some embodiments, the AN node is also configured to include the received SM context ID in the request to the SMF (for example, as part of the request URI of the Nsmf_PDUSession service).
[0152] In some embodiments, the SMF may also use the SM context ID in the request to identify the SM context and be configured to directly reply to the AN node that sent the request.
[0153] In some embodiments, the first request from the AN node to the SMF may include an AN Context ID, which may be used by the SMF and the AN node as a reference to the context of the UE in the AN node for any subsequent exchanges.
[0154] It should be appreciated that the following SM-related requests are suitable candidates for such direct signaling methods:
[0155] The N2 PDU Session Response and subsequent Nsmf_PDUSession_UpdateSMContext request during PDU Session Establishment will be replaced by the Nsmf_PDUSession_UpdateSMContext request;
[0156] The N2 path switch request during Xn-based HO and the subsequent Nsmf_PDUSession_UpdateSMContext request will be replaced by the Nsmf_PDUSession_UpdateSMcontext request;
[0157] The Nsmf_PDUSession_UpdateSMcontext request during N2-based HO will be sent directly by the T-RAN instead of by the T-AMF;
[0158] The Nsmf_PDUSession_UpdateSMcontext request during a service request will be sent directly by the (R)AN instead of by the AMF;
[0159] The N2 response reply (Ack) and subsequent Nsmf_PDUSession_UpdateSMcontext request during service activation will be replaced by the Nsmf_PDUSession_UpdateSMcontext request; and
[0160] PDU Session Resource Modification message, such as described in 3GPP TS 38.413.
[0161] about Figure 4 , shows an example flow chart of N2 interface SM related signaling from an AN node to an SMF, such as direct messaging according to some embodiments, and in particular an example of an Nsmf_PDUSession_UpdateSMcontext request.
[0162] exist Figure 4 In the example shown, there is an initial operation of AMF 402 generating a service request to 5GC NF 406, such as SMF, which service request may be, for example, a Nsmf_PDUSession_CreateSMContext request. The operation of generating and sending a service request is described in Figure 4 This is shown by step 401.
[0163] The 5GC NF 406 (e.g., SMF) may then generate a service response, which in some embodiments may include information such as Figure 4 The binding information shown in step 403.
[0164] The AMF 402 may then be configured to store the UE context, 5GC NF ID and possible information. Additionally, in some embodiments, the AMF is configured to store the SM context of the PDU session. The AMF storage operation is Figure 4 This is shown by step 405.
[0165] Block 407 illustrates a PDU session establishment / modification / service request according to some embodiments. The request process according to some embodiments includes the 5GC NF 406 being configured to generate and send a Namf_Communication_N1N2MessageTransfer (PDU Session ID) message to the AMF 402, such as Figure 4 As shown in step 409.
[0166] Then, if Figure 4 As shown in step 411, the AMF is configured to store the PDU session ID processed by the SMF.
[0167] The AMF may then be configured to generate an N2 PDU session request, which is passed to the AN node 400, such as a gNB, as shown in FIG. Figure 4 As shown in step 413 in . The N2 PDU session request, which may be designated as N2_PDU_Session_Request_Message, associated with the NGAP PDU session resource establishment request message may be extended and also triggered by the registration process. In other words, the AMF may be configured to provide not only the PDU session ID, but also the SM context ID, SMF ID / address / aggregate ID. In addition, in some cases, the message is extended to provide binding information as received in previous signaling from the SMF. In addition, in some embodiments, the message includes the SM context ID.
[0168] The AN node 400 may also be configured to cache or store PDU session ID values, such as SMF address / ID / aggregation ID, possible binding information, SM context ID, and PDU session ID, such as Figure 4 As shown in step 415.
[0169] Then, the AN node 400 may be configured to generate an NRF (Network Repository Function) 404 and send an NRF_NF_discovery message to the NRF 404, such as Figure 4 As shown in step 417. In some embodiments, the NRF_NF_discovery message includes the NF type (NF type = SMF) and the SMF set ID.
[0170] Then, the NRF 404 may be configured to generate a discovery response message and send it back to the AN node 400, such as Figure 4 As shown in step 419. In some embodiments, the discovery response message NRF_NF discovery response message includes SMF profile information (SMF profile 1, SMF profile 2).
[0171] Then, the AN node 400 is configured to generate an SM-related SB request and send it directly to the 5GC NF 406, such as Figure 4 As shown in step 421. In this example, a Msmf_PDUSession_UpdateSMContext request including a SM context ID value is shown.
[0172] like Figure 4 As shown in step 423, the 5GC NF 406 (e.g., SMF) is configured to generate a response and send it back to the AN node 400, such as Figure 4 As shown in step 423.
[0173] In some embodiments, the SMF may be configured to use the existing Namf_Communication_N1N2 message to deliver AMF services and in the N2 SM message (in Figure 5 SM context information, SMF set ID, and / or SMF instance ID, and / or SMF URI / SMF address, and optionally N2SMAP_SM_UE ID are provided in step 509 (shown as N2 container).
[0174] Therefore, in some embodiments, the N2 SM information can be transparently forwarded by the AMF to the AN node. The SMF includes these IEs (Information Elements) to enable the AN node to directly reach the SMF and the specific SM context (for a specific UE and PDU session) in the SMF in subsequent SM-related signaling.
[0175] For example, the SMF may include the SMF ID / address / set ID, binding information and SM context ID in the NGAP PDU session resource establishment request transport container IE to be relayed directly by the AMF to the AN node.
[0176] about Figure 5 , shows an example flow chart variant where the IE is signaled from the SMF to the AMF in an existing Namf_Communication_N1N2MessageTransfer format message.
[0177] exist Figure 5 In the example shown, there is an initial operation of AMF 402 generating a service request to 5GC NF 406, such as SMF, which service request may be, for example, Nsmf_PDUSession_CreateSMContext request. The operation of generating and sending the service request is described in Figure 5 This is shown by step 501.
[0178] The 5GC NF 406 (e.g., SMF) may then generate a service response, which in some embodiments may include information such as Figure 5 The binding information shown in step 503.
[0179] The AMF 402 may then be configured to store the UE context, 5GC NF ID and possible information. Additionally, in some embodiments, the AMF is configured to store the SM context of the PDU session. The AMF storage operation is Figure 5 This is shown by step 505.
[0180] Block 507 illustrates a PDU session establishment / modification / service request according to some embodiments.
[0181] The request process according to some embodiments includes the 5GC NF 406 being configured to generate an IE within a Namf_Communication_N1N2MessageTransfer message and send it to the AMF 402, such as Figure 5 As shown in step 509. Therefore, for example, Namf_Communication_N1N2MessageTransfer includes an N2_Container including an N2 PDU session request. The N2 PDU session request may include information elements such as PDU session ID, SMF address / ID / set ID, N2SM_SM_UE ID and SM context ID.
[0182] Then, AMF 402 is configured to store the PDU session ID processed by SMF, such as Figure 5 As shown in step 511.
[0183] The AMF 402 may then be configured to generate an N2 PDU session request, which is passed to the AN node 400, such as a gNB, as shown in FIG. Figure 5 As shown in step 513 in . The N2 PDU session request associated with the NGAP PDU session resource establishment request message can be extended, and the N2 PDU session request can be specified as N2_PDU_Session_Request_Message. In other words, the AMF can be configured to provide not only the PDU session ID, but also the SMF ID / address / aggregate ID and the N2 SM_SM_UE ID and SM context ID.
[0184] The AN node 400 may also be configured to cache or store PDU session ID values (such as SMF address / ID / aggregate ID, NGAP_SM_UE ID and PDU session ID) as part of the UE context information, such as Figure 5 As shown in step 515.
[0185] Then, the AN node 400 may be configured to generate an NRF_NF_discovery message and send it to the NRF (Network Repository Function) 404, such as Figure 5 As shown in step 517. In some embodiments, the NRF_NF_discovery message includes the NF type (NF type = SMF) and the SMF set ID.
[0186] Then, the NRF 404 may be configured to generate a discovery response message and send it back to the AN node 400, such as Figure 5As shown in step 519. In some embodiments, the discovery response message NRF_NF discovery response message includes SMF profile information (SMF profile 1, SMF profile 2).
[0187] Then, the AN node 400 can be configured to generate an SM-related SB request and send it directly to the 5GC NF 406, such as Figure 5 As shown in step 521 in the example, a Msmf_PDUSession_UpdateSMContext request including a SM context ID value is shown.
[0188] The 5GC NF 406 (e.g., SMF) is configured to generate an SM-related SB reply and send it back to the AN node 400, such as Figure 5 As shown in step 523.
[0189] In some embodiments, the N2 SM information also contains information that enables the AN node to send notifications to the SMF. In other words, the information includes the notification URI and possible notification association ID information and information about the events that the SMF expects to be notified.
[0190] In these embodiments, the AN node can use this information to send notifications to the indicated URIs when any of the indicated events occur. Possible notification correlation IDs are also included in those notifications. This enables the AN node to transmit the following message directly to the SMF (e.g., using a service operation similar to the Namf_Communication_N2InfoNotify service operation, but with the AN node as a service producer):
[0191] PDU Session Resource Notification (see TS 38.413)
[0192] PDU Session Resource Modification Indication (see TS 38.413)
[0193] As mentioned above, this concept of direct communication between access nodes and network functions is beneficial for network performance during handover. During handover (HO), the source NG-RAN transmits the stored SM context ID together with the SMF identifier (SMF ID and / or SMF address and / or SMF URI and / or SMF set ID and possible additional information derived from the received binding information) to the target NG-RAN over the Xn interface. The target NG-RAN is then configured to use the received context and binding information to reach the SMF directly.
[0194] about Figure 6 , a signaling flow chart illustrating an example of the direct communication embodiment is shown.
[0195] Therefore, if Figure 6 As shown in step 601, UE 600, source NG-RAN 602 and target NG-RAN 604 participate in handover preparation.
[0196] The handover execution process is then performed as shown in block 603. With respect to these embodiments, the handover execution process includes forwarding data from the source NG-RAN 602 to the target NG-RAN 604, such as Figure 6 As shown in step 605. In addition, Figure 6 As shown in step 607, the handover execution process may also include generating a RAN usage report from the source NG-RAN 602 and sending it to the AMF 606.
[0197] A UE context transfer message including the cached SMF set ID, SMF instance and SM context ID may then be generated and delivered from the source NG-RAN 602 to the target NGRAN 604, as shown in FIG. Figure 6 As shown in step 609.
[0198] like Figure 6 The target NG-RAN 604 shown in step 611 in FIG. 6 is configured to use the SMF set ID / instance information to implement NRF interaction for SMF discovery.
[0199] Then, based on the result of the discovery, the target NG-RAN 604 is configured to generate an Nsmf_PDUSession_UpdateSMContext request including the SM context ID and pass it to the discovered SMF 608, as shown in FIG. Figure 6 As shown in step 613.
[0200] Then, if Figure 6 As shown in step 615, (multiple) SMF 608 can be configured to generate an N4 session modification request and send it to (multiple) UPF 610.
[0201] The UPF(s) 610 may also be configured to generate an N4 session modification response in response to the N4 session modification request and send it back to the SMF(s) 608, such as Figure 6 As shown in step 617.
[0202] The UPF(s) 610 are also configured to generate an N3 end marker and send it to the source NG-RAN 602, such as Figure 6 As shown in step 619.
[0203] The source NG-RAN 602 forwards the received N3 end marker to the target NG-RAN 604, as shown in FIG. Figure 6 As shown in step 621.
[0204] The UPF(s) 610 may also be configured to generate downlink data and send it to the UE 600, such as Figure 6 As shown in step 623.
[0205] like Figure 6 As shown in step 625, (multiple) SMF 608 is configured to generate an Nsmf_PDUSession_UpdateSMContext response and send it to AMF 606.
[0206] The AMF 606 may then be configured to send an N2 Path Switch Request Confirm message to the target NG-RAN 604, such as Figure 6 As shown in step 627.
[0207] After this, the target NG-RAN 604 is configured to generate a Release Resources message and pass it to the source NG-RAN 602, such as Figure 6 As shown in step 629.
[0208] like Figure 6 As shown in step 631, the registration process between UE 600, source NG-RAN 602, target NG-RAN 604 and AMF 606 is implemented and completed.
[0209] In some embodiments, PDU-related direct signaling (which also applies to non-PDU session-related signaling) can implement the introduced AMF core network function discovery service operation.
[0210] The operation may have as input: a UE temporary entity or UE context identifier in the AMF, e.g. AMF UENGAP ID or GUTI, possible network function types (e.g. SMF, SMSF, PCF, LMF, AMF) and / or service types for SMF, PDU session ID.
[0211] Furthermore, the operation may have as output: NF ID / address / set ID, possible binding information of the requested type of 5GC NF / service handling the UE context / PDU session, possible SM context ID for the PDU session.
[0212] The AN node may then be configured to address subsequent UE context or PDU session related service-based (SB) requests directly to the 5GC NF using the received NF ID / address / set ID and information derived from the received binding information.
[0213] Therefore, in some embodiments, the AN node can use this information to query the configuration file of the 5GC NF at the NRF.
[0214] The AN node can also delegate 5GC NF discovery to the SCP and provide this information as discovery parameters.
[0215] The AN node may also include binding information equivalent to the binding information received in the request to the 5GC NF.
[0216] If the SB Request contains the AMF UE NGAP ID, it also contains the AMF ID.
[0217] Furthermore, in some embodiments, the following items may be introduced to enable the 5GC NF to interpret the AMF UE NGAP ID as the UE ID received from the AN node in direct signalling.
[0218] These operations include the introduction of a new AMF UE Identity Mapping service operation (for non-PDU session related services). Thus, in some embodiments, the service operation may include as input an AMF UE NGAP ID and an output SUPI. Furthermore, access may be restricted to 5GC network elements. The 5GC NF addresses the AMF previously indicated in the SB Request including the AMF UE NGAP ID to invoke the service operation.
[0219] In some embodiments, as an alternative, the AMF may be configured to signal the AMF the UE NGAP ID identifier in existing interactions with the 5GC NF to avoid the need for a query.
[0220] This can be seen for example in Figure 7 Shown.
[0221] like Figure 7 As shown in step 701, AMF 402 has stored the UE context.
[0222] AMF 402 is also configured to communicate with 5GC NF (e.g., SMF 406) based on the service request or response (including AMF UE NGAP ID), such as Figure 7 As shown in step 703.
[0223] The AN node 400 is configured to generate an AMF_CMF_discovery message and send it to the AMF 402, such as Figure 7 As shown in step 705. The discovery message includes the AMF UE NGAP ID or GUTI, and may also include a PDU session ID, NF type and / or service type.
[0224] Then, if Figure 7As shown in step 707 in , AMF 402 is configured to respond to the AMF_CMF_discovery message with an appropriate AMF_CMF_discovery response message. In some embodiments, the response message includes 5GC NF address / ID / set ID, binding information and possible SM context ID.
[0225] The AN node 400 is also configured to cache or store the 5GC NF for the AMF UE NGAP ID and possible PDU sessions, such as Figure 7 As shown in step 709.
[0226] Then, the AN node 400 may be configured to generate an NRF_NF_discovery message and send it to the NRF (Network Repository Function) 404, such as Figure 7 As shown in step 711. In some embodiments, the NRF_NF_discovery message includes the NF type (NF type = SMF) and the SMF set ID.
[0227] Then, the NRF 404 may be configured to generate a discovery response message and send it back to the AN node 400, such as Figure 7 As shown in step 713. In some embodiments, the discovery response message NRF_NF discovery response message includes SMF profile information (SMF profile 1, SMF profile 2, etc.).
[0228] Then, the AN node 400 is configured to generate an SMF request and send it directly to the 5GC NF 406, such as Figure 7 As shown in step 715.
[0229] Then, the 5GC NF (SMF) 406 is configured to generate an AMF_UE_Identity_Map message and send it to the AMF 402, which Figure 7 As shown by step 717. The AMF_UE_Identity_Map message in some embodiments includes the AMF UE N GAP ID information element.
[0230] The AMF 402 is then configured to generate and send a response to the AMF_UE_Identity_Map message in the form of an AMF_US_Identity_Map response to the 5GC NF (SMF) 406. Figure 7 , as shown by step 719. In some embodiments, the AMF_UE_Identity_Map response message includes a SUPI (Subscriber Permanent Identifier) element.
[0231] The 5GC NF (SMF) 406 may then be configured to cache or store the SUPI for the AMF US NGAP ID, such as Figure 7 As shown in step 721.
[0232] In some embodiments, MBS (Multicast and Broadcast Service) extensions may be implemented, where the RAN node needs to be able to discover the MB-SMF handling the MBS session and communicate directly with the associated MB-SMF. In some embodiments, the extension of MBS may be implemented by the method described above and with the following changes:
[0233] Replace SMF ID / address / aggregate ID with MB-SMF ID / address / aggregate ID;
[0234] The operation of using the SM context ID to identify a specific UE is replaced by using the MBS session ID to identify a specific MBS session.
[0235] In implementing the embodiments discussed in detail above, the following advantages may be obtained. Embodiments allow SMF (or other core NF) services to be addressed directly by AN nodes. Furthermore, in some embodiments, SMF session management services or notifications may be invoked directly by the gNB. This may be particularly advantageous during a transition phase where only certain direct communications are enabled and the AMF is configured to be aware of the gNB from other interactions. Additionally, as described above, embodiments provide an improved Xn-based handover process.
[0236] It should be understood that the apparatus may include or be coupled to other units or modules, etc., such as a radio part or radio head used in or for transmission and / or reception. Although the apparatus has been described as one entity, different modules and memories may be implemented in one or more physical or logical entities.
[0237] Note that while some embodiments have been described with respect to 5G networks, similar principles may be applied with respect to other networks and communication systems. Thus, while certain embodiments are described above by way of example with reference to certain example architectures for wireless networks, technologies, and standards, the embodiments may be applied to any other suitable form of communication system in addition to the communication system shown and described herein.
[0238] It is also noted here that while the above describes exemplifying embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.
[0239] In general, various embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, but the disclosure is not limited thereto. Although various aspects of the disclosure may be shown and described as block diagrams, flow charts, or using some other graphical representation, it is well understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general purpose hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.
[0240] As used in this application, the term "circuitry" may refer to one, more, or all of the following:
[0241] (a) only hardware circuit implementation (e.g., only implementation in analog and / or digital circuitry) and
[0242] (b) a combination of hardware circuitry and software such as (where applicable):
[0243] (i) a combination of analog and / or digital hardware circuits and software / firmware, and
[0244] (ii) any portion of hardware processor(s) with software (including digital signal processor(s)) together with software and memory(s) that work together to enable a device such as a mobile phone or server to perform various functions) and
[0245] (c) Hardware circuit(s) and / or processor(s) (such as a microprocessor or a portion of a microprocessor) that require software (e.g., firmware) to operate, but where software is not required to operate, the software may not be present.
[0246] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or its) accompanying software and / or firmware. The term circuitry also covers (for example and if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.
[0247] Embodiments of the present invention may be implemented by computer software executable by a data processor of a mobile device (e.g., in a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs, also referred to as program products, include software routines, applets, and / or macros that may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform various embodiments when the program is running. One or more computer executable components may be at least one software code or a portion thereof.
[0248] Also, at this point it should be noted that any block of the logic flow in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on physical media such as memory chips or memory blocks implemented within the processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants, CDs. Physical media are non-transitory media.
[0249] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. As non-limiting examples, the data processor may be of any type suitable for the local technical environment and may include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.
[0250] Embodiments of the present disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.
[0251] The scope of protection sought by various embodiments of the present disclosure is set out by the independent claims. Embodiments and features described in this specification that do not fall within the scope of the independent claims, if any, are to be interpreted as examples useful for understanding various embodiments of the present disclosure.
[0252] The above description has provided a complete and informative description of exemplary embodiments of the present disclosure by way of non-limiting examples. However, when read in conjunction with the accompanying drawings and the appended claims, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the foregoing description. However, all of these and similar modifications of the teachings of the present disclosure will still fall within the scope of the present invention as defined by the appended claims. In fact, there are other embodiments that include a combination of one or more embodiments with any of the other embodiments previously discussed.
Claims
1. An apparatus, network node or entity comprising means for: Obtain an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function; as well as The network function identifier is provided to an access node associated with the user equipment identifier and / or with a session matching the network function context identifier.
2. The apparatus or entity of claim 1, wherein the network function identifier enables the access node to directly access the network function associated with the network function identifier.
3. The apparatus or entity according to claim 1 or 2, further comprising: Means for providing a session identifier to said access node.
4. The apparatus or entity according to any one of claims 1 to 3, wherein the network function identifier comprises at least one of the following: The network address of the network function; and An identifier of a network function set comprising the network function.
5. The apparatus or entity according to any one of claims 1 to 4, wherein the means for obtaining the information element is for receiving the information element from the network function.
6. The apparatus or entity of claim 5, wherein the means for receiving the information element from the network function is configured to receive the information element within an N2 interface message container.
7. The apparatus or entity according to any one of claims 1 to 6, wherein the information element further comprises: Session identifier.
8. The apparatus or entity according to any one of claims 1 to 7, wherein the information element further comprises: Binding information.
9. The apparatus or entity according to any one of claims 1 to 8, wherein the means for providing the information element to the access node is configured to generate and provide at least one of: An interface protocol data unit session request, the interface protocol data unit session request comprising: said information element from an access and mobility function node to said access node; as well as A discovery response comprising: an information element from the access and mobility function node to the access node.
10. An apparatus or entity according to any one of claims 1 to 9, wherein the component for obtaining the information element is also used to receive the network function context identifier, the network function identifier and the session identifier in an Nsmf_PDUSession_CreateSMContext response, and the component is also used to store the information element in a context associated with the identified session.
11. An apparatus or entity according to any one of claims 1 to 10, wherein the means for providing the network function identifier is further configured to include the network function context identifier; and a network function identifier in an N2 PDU session request when receiving a Namf_Communication_N1N2Message transmission message.
12. An apparatus or entity according to any one of claims 1 to 11, wherein the component is further used for: Receive a Namf_Communication_N1N2Message delivery request containing a session identifier, and In response to receiving the Namf_Communication_N1N2 messaging request, providing the network function identifier to the access node associated with the session identified by the session identifier.
13. An apparatus or entity according to any one of claims 1 to 12, wherein the means for obtaining an information element is further for: receiving the user equipment identifier, the user equipment identifier being associated with a first user equipment and the network function identifier; and The user equipment identifier associated with the first user equipment and the network function identifier is stored in a context associated with the identified first user equipment.
14. The apparatus or entity of claim 13, wherein the means is further configured to provide the network function with a second user equipment identifier associated with the first user equipment.
15. The apparatus or entity according to any one of claims 1 to 14, wherein the user equipment identifier is a first user equipment identifier, and the means is further configured to receive a discovery request user equipment identifier from the access node, wherein the discovery request comprises at least one of the following: a second user device identifier; Session identifier; and The type of network capabilities to discover.
16. The apparatus or entity according to any one of claims 1 to 15, wherein the network node comprises: Access and mobility function node.
17. The apparatus or entity according to any one of claims 1 to 16, wherein the network function associated with the network function identifier comprises: Session management capabilities.
18. An apparatus or entity, access node, comprising means for: Receive an information element, the information element comprising: a network function identifier associated with the network function; as well as The information element is employed to directly access the network function associated with the network function identifier.
19. The apparatus or entity of claim 18, wherein the network function identifier comprises at least one of the following: The network address of the network function; and An identifier of a network function set comprising the network function.
20. An apparatus or entity according to any one of claims 18 or 19, wherein the information element also includes a network function context identifier; and the component for using the information element to directly access the network function associated with the network function identifier is also used to: provide the network function context identifier in a request for the network function.
21. An apparatus or entity according to any one of claims 18 to 20, wherein said means is further for storing said information element.
22. An apparatus or entity according to any one of claims 18 to 21, wherein the means is further configured to forward the information element to a target access node as part of a user equipment context transfer.
23. An apparatus or entity according to any of claims 18 to 22, wherein the means for receiving the information element is for receiving the information element from a second network function.
24. The apparatus or entity of claim 23, wherein the means for receiving the information element from the second network function is configured to receive the information element according to one of the following: An interface protocol data unit session request, the interface protocol data unit session request comprising: said information elements from access and mobility functions; A user equipment context transmission, the user equipment context transmission comprising: the information element from a source access node; and A discovery response comprising: the information element from an access and mobility function node.
25. The apparatus or entity of any one of claims 23 or 24, wherein the apparatus is further configured to request discovery of the network function from the second network function, wherein the request for discovery comprises at least one of: User device identifier; Session identifier; and The type of network capabilities to discover.
26. An apparatus or entity according to any one of claims 18 to 25, wherein the information element further comprises: Session identifier.
27. An apparatus or entity according to any one of claims 18 to 26, wherein the information element further comprises: Binding information.
28. An apparatus or entity according to any one of claims 18 to 27, wherein the means for employing the information element to directly access the network function associated with the network function address / identifier / aggregate identifier is for: generating a discovery message including the network set identifier, and obtaining a response indicating to communicate directly with the network function; and A request is generated to communicate directly with the indicated network function.
29. An apparatus or entity, session management function, comprising means for: The session management container is sent in the Namf_Communication_N1N2Message transmission request, wherein the session management container includes: an identifier of a session, an identifier of a session management function, and an identifier of a session management context associated with the session; as well as A request related to the session is received from an access node, wherein the request includes the identifier of the session management context.
30. The apparatus or entity of claim 29, wherein the identifier of the session management function comprises at least one of: the network address of the session management function, and An identifier of a set of session management functions that includes the session management function.
31. A method for a network node or entity, the method comprising: obtaining an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function; and The network function identifier is provided to an access node associated with the user equipment identifier and / or with a session matching the network function context identifier.
32. A method for accessing a node, the method comprising: receiving an information element comprising: a network function identifier associated with a network function; and The information element is employed to directly access the network function associated with the network function identifier.
33. A method for session management functionality, the method comprising: Sending a session management container in a Namf_Communication_N1N2Message transmission request, wherein the session management container includes: an identifier of a session, an identifier of a session management function, and an identifier of a session management context associated with the session; and A request related to the session is received from an access node, wherein the request includes the identifier of the session management context.
34. A computer program comprising instructions or a computer readable medium containing program instructions for causing a network node or entity to at least: Obtain an information element, the information element comprising: a network function context identifier and / or a user equipment identifier; and a network function identifier associated with the network function; as well as The network function identifier is provided to an access node associated with the user equipment identifier and / or with a session matching the network function context identifier.
35. A computer program comprising instructions or a computer readable medium containing program instructions for causing a network node or entity to at least: Receive an information element, the information element comprising: a network function identifier associated with the network function; as well as The information element is employed to directly access the network function associated with the network function identifier.
36. A computer program comprising instructions or a computer readable medium containing program instructions for causing a network node or entity to at least: The session management container is sent in the Namf_Communication_N1N2Message transmission request, wherein the session management container includes: an identification of a session, an identifier of a session management function, and an identifier of a session management context associated with the session; as well as A request related to the session is received from an access node, wherein the request includes an identifier of the session management context.
