PCF device, AF device, NEF device, and methods thereof
The AF device and core network devices enable 5G systems to quickly select and hand over UE to specific cells like FR2, optimizing user experience by setting up user plane paths based on AF requests, addressing the challenge of network inefficiencies in existing protocols.
Patent Information
- Application Number
- JP2020078448
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-04-27
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-04-27
AI Technical Summary
Existing wireless communication networks, particularly 5G systems, face challenges in quickly selecting and handing over user equipment (UE) to specific cells, such as FR2 cells, to optimize user experience for services like large-capacity content distribution and online gaming, as existing protocols do not allow for direct control of user plane paths to include these cells based on application function (AF) requests.
An Application Function (AF) device and core network devices are configured to send and receive messages to set up or modify user plane paths, enabling user data transfer via a radio connection of a particular cell, such as FR2, through mechanisms like dual connectivity or handover, based on AF requests.
This solution allows wireless communication networks to provide UE with optimized user plane paths including specific cell connections, enhancing user experience by ensuring efficient data transfer and service delivery.
Smart Images

Figure 0007593610000001 
Figure 0007593610000002 
Figure 0007593610000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to wireless communication networks, and more particularly to user plane path control. [Background technology]
[0002] Patent Document 1 discloses handing over a mobile terminal from a macrocell to a specific small cell so that the mobile terminal can use a special service provided only in the small cell. In one example disclosed in Patent Document 1, a mobile terminal is present in a macrocell provided by a radio base station (hereinafter referred to as a macrocell base station) and transmits a service establishment request for establishing a specific service to a core network node via the macrocell base station. The core network node is, for example, a Serving GPRS Support Node (SGSN) or a Mobility Management Entity (MME). In response to receiving the service establishment request from the mobile terminal, the core network node requests the macrocell base station to establish the requested specific service. The macrocell base station manages a table indicating which type of specific service is provided in each of a plurality of small cells. The macrocell base station selects a small cell associated with the requested specific service based on the table, and determines whether or not the mobile terminal can be handed over to the selected small cell. The determination is made based on, for example, whether or not radio waves of a predetermined strength or more are received from the mobile terminal at the macrocell base station. If it is determined that the mobile terminal can be handed over to the selected small cell, the macro cell base station transmits a response indicating failure of service establishment to the core network node, and hands over the mobile station to the selected small cell. After completion of the handover, the radio base station providing the small cell (hereinafter referred to as the small cell base station) notifies the core network node of the completion of the handover. After completion of the handover, the core network node requests the small cell base station to establish a specific service.
[0003] In another example disclosed in Patent Document 1, the above-mentioned table is managed by a core network node (eg, SGSN or MME) rather than by a macrocell base station. Specifically, in response to receiving a service establishment request from a mobile terminal via a macrocell base station, the core network node refers to a table associated with the macrocell base station, selects a small cell associated with the requested specific service, and determines whether or not the mobile terminal can be handed over to the selected small cell. The determination is made, for example, based on whether or not a radio wave of a predetermined strength or more is received from the mobile terminal at the macrocell base station. If it is determined that the mobile terminal can be handed over to the selected small cell, the core network node requests the macrocell base station to execute the handover. In response to the handover execution request from the core network node, the macrocell base station hands over the mobile station from the macrocell to the small cell. After the handover is completed, the small cell base station notifies the core network node of the handover completion. After the handover is completed, the core network node requests the small cell base station to establish the specific service.
[0004] On the other hand, Non-Patent Document 1 (e.g., Section 5.6.7) and Non-Patent Document 2 (e.g., Section 4.3.6) disclose Application Function (AF) influence on traffic routing. AF influence on traffic routing is a control plane solution that enables an AF to provide input to a 5G Core Network (5GC) on how certain traffic should be routed. More specifically, an AF sends requests to a 5GC to influence routing decisions by a Session Management Function (SMF) regarding the traffic (i.e., one or more QoS Flows) of a Protocol Data Unit (PDU) session. For example, AF requests can influence a User Plane Function (UPF) selection by the SMF to route user traffic to a local access to a Data Network (DN) identified by a DN Access Identifier (DNAI). The UPF selection by the SMF involves the insertion of a UL Classifier (ULCL) UPF or a Branching Point (BP) UPF into the User Plane (UP) path of the PDU session. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] International Publication No. 2014 / 013646 [Non-patent literature]
[0006] [Non-Patent Document 1] 3GPP TS 23.501 V16.3.0 (2019-12) "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 16)", December 2019 [Non-Patent Document 2] 3GPP TS 23.502 V16.3.0 (2019-12) "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16)", December 2019 Summary of the Invention [Problem to be solved by the invention]
[0007] The 5G system supports millimeter wave frequency bands from 4.25 GHz to 52.6 GHz in addition to the sub-6 GHz frequency bands also used in Long Term Evolution (LTE). The sub-6 GHz frequency bands are called Frequency Range 1 (FR1), and the millimeter wave frequency bands are called Frequency Range 2 (FR2). By using the FR2 bands, 5G Next Radio (NR) devices can exchange data over a wider carrier bandwidth and achieve very low scheduling latencies. However, considering the propagation characteristics of millimeter waves, FR2 cells will be local cells or small cells located within FR1 cells.
[0008] The inventors have considered an improvement to enable a wireless communication network (eg, 5G system) to quickly select a specific cell (e.g., a cell operating in a specific frequency band (eg, FR2)) suitable for a specific service when a wireless terminal (hereinafter, referred to as User Equipment (UE)) desires the specific service. For example, an application server that communicates with an application in the UE via the wireless communication network (eg, 5G system) can receive from the UE at the application layer a report of cells available to the UE. Therefore, if the application server (or a control server linked thereto) can request the wireless communication network (eg, 5G system) to provide the UE with a UP path including a wireless connection of a specific cell (eg, FR2 cell), this may contribute to improving the user experience.
[0009] Patent Document 1 does not disclose, for example, that an application function (AF) requests a core network to handover a UE to a specific cell (e.g., FR2 cell). On the other hand, the AF influence on traffic routing described in Non-Patent Documents 1 and 2 enables the AF to request a core network to change an UP route. However, Non-Patent Documents 1 and 2 do not disclose a procedure in which the AF requests the core network to provide an UP route including a radio connection of a specific cell (e.g., FR2 cell).
[0010] One of the objectives to be achieved by the embodiments disclosed herein is to provide an apparatus, a method, and a program that contribute to enabling a wireless communication network to provide a UE with a UP path including a radio connection of a specific cell based on a request from an application function (AF). Note that this objective is only one of the objectives to be achieved by the embodiments disclosed herein. Other objectives or problems and novel features will be apparent from the description of this specification or the accompanying drawings. [Means for solving the problem]
[0011] In a first aspect, an Application Function (AF) device includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to transmit a first message to a core network, the first message requesting the core network to set up or modify a user plane path such that user data for a User Equipment (UE) is forwarded via the user plane path including a radio connection of a particular cell.
[0012] In a second aspect, a core network device includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive a second message from another core network node based on a request from an Application Function (AF), the at least one processor further configured to, in response to the second message, request a Radio Access Network (RAN) to set up or modify a user plane path such that user data for a User Equipment (UE) is forwarded via the user plane path including a radio connection of a particular cell.
[0013] In a third aspect, a method performed by an Application Function (AF) device includes transmitting a first message to a core network, the first message requesting the core network to set up or modify a user plane path such that user data for User Equipment (UE) is forwarded via the user plane path that includes a radio connection of a particular cell.
[0014] In a fourth aspect, a method performed by a core network device includes the following steps: (a) receiving a second message from another core network node based on a request from an Application Function (AF); and (b) in response to the second message, requesting a Radio Access Network (RAN) to set up or modify a user plane path such that user data for User Equipment (UE) is forwarded via a user plane path that includes a radio connection of a particular cell.
[0015] In a fifth aspect, a program includes a set of instructions (software code) for causing a computer to carry out the method according to the third or fourth aspect above when the program is loaded into the computer. Effect of the Invention
[0016] According to the above-described aspects, it is possible to provide an apparatus, a method, and a program that contribute to enabling a wireless communication network to provide a UE with a UP path including a radio connection of a specific cell based on a request from an application function (AF). [Brief description of the drawings]
[0017] [Figure 1] 1 is a diagram illustrating an example of the configuration of a wireless communication network according to an embodiment. [Diagram 2] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 3A] A diagram showing an example of a user plane path before dual connectivity or handover occurs. [Figure 3B] A diagram showing an example of a user plane path after dual connectivity is initiated. [Figure 3C] A diagram showing an example of a user plane path after dual connectivity is initiated. [Figure 3D] A diagram showing an example of a user plane path after handover. [Figure 3E] A diagram showing an example of a user plane path after handover. [Figure 4] 10 is a flowchart illustrating an example of an operation of an application function according to the embodiment. [Diagram 5] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 6] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 7] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 8] FIG. 11 is a sequence diagram showing an example of signaling according to an embodiment. [Figure 9] FIG. 2 is a block diagram showing a configuration example of a RAN node according to the embodiment. [Figure 10] FIG. 2 is a block diagram showing an example of the configuration of a UE according to the embodiment. [Figure 11] FIG. 2 is a block diagram showing an example of the configuration of an application function according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0018] In the following, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and duplicated descriptions will be omitted as necessary for clarity of explanation.
[0019] The multiple embodiments described below can be implemented independently or in appropriate combination. These multiple embodiments have different novel features. Therefore, these multiple embodiments contribute to solving different objects or problems and provide different effects.
[0020] The following embodiments will be described with a focus on a fifth generation mobile communication system (5G system (5GS)). However, these embodiments may be applied to other wireless communication systems (eg, LTE system).
[0021] <First embodiment> FIG. 1 illustrates an example of the configuration of a wireless communication network (i.e., 5GS) according to some embodiments including the present embodiment. Each of the elements illustrated in FIG. 1 is a network function, and provides an interface defined by the 3rd Generation Partnership Project (3GPP). Each of the elements (network functions) illustrated in FIG. 1 can be implemented, for example, as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an application platform.
[0022] The wireless communication network shown in Fig. 1 may be provided by a Mobile Network Operator (MNO) or may be a Non-Public Network (NPN) provided by a party other than an MNO. When the wireless communication network shown in Fig. 1 is an NPN, it may be an independent network represented as a Stand-alone Non-Public Network (SNPN) or an NPN linked with an MNO network represented as a Public network integrated NPN.
[0023] In the example of FIG. 1, the wireless communication network includes a Radio Access Network (RAN) 10, a 5G Core Network (5GC) 30, and an Application Function (AF) 41. The RAN 10 includes RAN nodes 1 and 2. The 5GC 30 includes an Access and Mobility Management Function (AMF) 31, a Session Management Function (SMF) 32, a User Plane Function (UPF) 33, a Policy Control Function (PCF) 34, and a Network Exposure Function (NEF) 35.
[0024] Each of the RAN nodes 1 and 2 may be a gNB or an ng-eNB. The RAN nodes 1 and 2 may be a Central Unit (eg, gNB-CU) in a cloud RAN (C-RAN) deployment. The RAN node 1 terminates a Control Plane (CP) interface (i.e., N2 interface) with the 5GC 30 and interworks with the AMF 31 in the 5GS 30 over the CP interface. In some implementations, the RAN node 2 may also terminate a CP interface (i.e., N2 interface) with the 5GC 30 and interwork with the AMF 31 over the CP interface. In other implementations, the RAN node 2 may not have a CP interface with any AMF. For example, if the RAN node 2 is responsible for only a secondary node (SN) of Dual Connectivity (DC) in a non-standalone deployment, the RAN node 2 may not have a CP interface with the 5GC 30.
[0025] RAN node 1 provides one or more cells including cell 11, and RAN node 2 provides one or more cells including cell 12. Cell 11 may operate in a different frequency band than cell 12. For example, cell 11 may operate in any sub-6 GHz frequency band in FR1, and cell 12 may operate in any mmWave frequency band in FR2. As shown in FIG. 1, cell 12 in the higher frequency band may be a local cell (small cell) located within cell 11 in the lower frequency band. Cell 11 may completely cover cell 12 or may partially overlap with cell 12.
[0026] The AMF 31 is one of the network functions in the 5GC control plane. The AMF 31 provides the termination of the RAN CP interface (i.e., N2 interface). The AMF 31 terminates a single signaling connection (i.e., N1 Non-Access Stratum (NAS) signalling connection) with the UE 3 and provides registration management, connection management, and mobility management. Additionally, the AMF 31 provides NF services to NF consumers (e.g., other AMFs, SMF 32, and Authentication Server Function (AUSF)) over a service-based interface (i.e., Namf interface). Furthermore, the AMF 31 consumes NF services provided by other NFs (e.g., Unified Data Management (UDM), Network Slice Selection Function (NSSF), and PCF 34).
[0027] The SMF32 is one of the network functions in the 5GC control plane. The SMF32 manages PDU sessions. The SMF32 transmits and receives SM signaling messages (NAS-SM messages) to and from the Non-Access Stratum (NAS) Session Management (SM) layer of the UE3 via the communication service provided by the AMF31. The SMF32 provides NF services to NF consumers (e.g., AMF31, other SMFs) over a service-based interface (i.e., Nsmf interface). The NF services provided by the SMF32 include a PDU session management service (Nsmf_PDUSession). The NF services allow NF consumers (e.g., AMF31) to handle PDU sessions. The SMF32 may be an Intermediate SMF (I-SMF). The I-SMF is inserted between the AMF 31 and the original SMF as necessary when the UPF 33 belongs to a different SMF service area and cannot be controlled by the original SMF.
[0028] The UPF 33 is one of the network functions in the 5GC user plane. The UPF 33 processes and forwards user data. The functionality of the UPF 33 is controlled by the SMF 32. The UPF 33 interconnects with the data network (DN) 50 and acts as an anchor point toward the DN 50 for one or more PDU sessions of the UE 3. The UPF 33 may include multiple UPFs interconnected via an N9 interface. More specifically, the UP path for the PDU session of the UE 3 may include one or more PDU Session Anchor (PSA) UPFs, may include one or more Intermediate UPFs (I-UPFs), and may include one or more Uplink Classifier (UL CL) UPFs (or Branching Point (BP) UPFs).
[0029] The PCF 34 provides various policy controls, including policy control for session management related functions and policy control for access and mobility related functions. For example, the PCF 34 interacts with the AF 41 directly or via the NEF 35 (via the N5 interface) and with the SMF 32 (via the N7 interface) for session management related policy control.
[0030] The NEF35 has a role similar to the Service Capability Exposure Function (SCEF) of the Evolved Packet System (EPS). Specifically, the NEF35 supports the exposure of services and capabilities from 5G systems to applications and network functions inside and outside the operator network.
[0031] A wireless terminal (ie, UE) 3 uses a 5G connectivity service to communicate with a data network (DN) 50. More specifically, the UE 3 is connected to the RAN 10 and communicates with the DN 50 at the application layer via the UPF 33 in the 5G GC 30. Note that the term "application layer" in this specification means all protocol layers above the PDU session (PDU session layer) between the UE 3 and the DN 50 provided by the 5GS. For example, if the PDUs are IP packets, the application layer includes application protocols such as Hypertext Transfer Protocol (HTTP) and File Transfer Protocol (FTP), as well as transport layer protocols between the IP and the application protocols (e.g., User Datagram Protocol (UDP) and Transmission Control Protocol (TCP)).
[0032] The AF 41 interacts with the PCF 34 to request policy control for the PDU session of the UE 3 from the 5GC 30. As described above, the AF 41 interacts with the PCF 34 directly or via the NEF 35. In addition, in the example of FIG. 1, the AF 41 can communicate with an application (UE application) running on a processor of the UE 3 via the DN 50 (e.g., the internet or other IP network) and a PDU session between the DN 50 and the UE 3. The AF 41 may include one or more computers. For example, the AF 41 may include one or more servers (e.g., content distribution server, online game server) that communicate with the UE 3 at the application layer, and a controller (i.e., an AF in the 3GPP definition) that cooperates with the one or more servers and interacts with the 5GC 30 (e.g., PCF 34). Furthermore, the AF 41 may include multiple servers that are distributed. For example, the AF 41 may include one or more edge computing servers located near the RAN 10 in addition to a central server. The edge computing servers and the local UPF that provides steering of user plane traffic for local access to the edge computing servers may be collocated with any RAN node or at a network aggregation site between the RAN 10 and the CN 30.
[0033] For convenience of explanation, only representative NFs are shown in the configuration example of Fig. 1. The wireless communication network according to the present embodiment may include other NFs not shown in Fig. 1.
[0034] Figure 2 shows an example of signaling according to this embodiment. According to the procedure of Figure 2, based on a request from the AF 41, the 5GC 30 and the RAN 10 set up or modify an UP path including a radio connection (e.g., Data Radio Bearer (DRB)) of a particular cell such that user data belonging to a PDU session of the UE 3 is forwarded via the UP path. The user data belonging to the PDU session of the UE 3 may be one or more Quality of Service (QoS) flows.
[0035] The UP path includes an N3 tunnel between the UPF 33 (specifically, the PSA UPF) in the 5GC 30 and the RAN 10 (specifically, the RAN node 1 or 2), and a radio connection (DRB) between the RAN 10 (specifically, the RAN node 1 or 2) and the UE 3. If multiple UPFs are used for a PDU session, the UP path may further include one or more N9 tunnels between the UPFs. The N3 tunnel and the N9 tunnel may be General Packet Radio Service (GPRS) Tunnelling Protocol for User Plane (GTP-U) tunnels.
[0036] The procedure shown in Fig. 2 is initiated (or triggered) by the AF 41 when the UE 3 is camped on a cell 11 (e.g., FR1 macro cell) provided by the RAN node 1. The AF 41 requests the 5GC 30 to move traffic (i.e., one or more QoS flows) belonging to a PDU session of the UE 3 to a UP path passing through a cell 12 (e.g., FR2 local cell) provided by the RAN node 2. Thus, here, the particular cell is the cell 12 provided by the RAN node 2.
[0037] In step 201, the AF 41 sends an AF request to the 5GC 30. Specifically, the AF 41 sends the AF request to the PCF 34 directly or via the NEF 35. The AF request requests the 5GC 30 to set up or modify an UP path such that user data belonging to a PDU session for the UE 3 is forwarded via an UP path including a radio connection of the cell 12. In other words, the AF request requests the 5GC 30 to modify an established PDU session for the UE 3 such that user data belonging to the established PDU session is forwarded via an UP path including a radio connection of the cell 12.
[0038] In some implementations, the AF request may cause the 5GC 30 to control the RAN 10 to add the cell 12 as a secondary cell (Secondary Cell Group (SCG) cell) of the dual connectivity (DC) for the UE 3. In other words, the AF 41 may request the 5GC 30 to add the cell 12 as an SCG cell of the DC for the UE 3 via the AF request.
[0039] Dual connectivity enables a UE to simultaneously use a Master Cell Group (MCG) provided by a Master Node (MN) (e.g., RAN node 1) and a Secondary Cell Group (SCG) provided by a Secondary Node (SN) (e.g., RAN node 2). An MCG is a group of serving cells associated with (or provided by) a RAN node (e.g., RAN node 1) acting as an MN of a DC, and includes an SpCell (i.e., a Primary Cell (PCell)) and, optionally, one or more Secondary Cells (SCells). On the other hand, an SCG is a group of serving cells associated with (or provided by) a RAN node (e.g., RAN node 2) acting as an SN of a DC, and includes an SCG primary cell and, optionally, one or more Secondary Cells (SCells). The SCG primary cell is the Primary SCG Cell (PSCell) or the Primary Secondary Cell (PSCell). The PSCell is the SCG Special Cell (SpCell).
[0040] In other implementations, the AF request may cause the 5GC 30 to control the RAN 10 to hand over the UE 3 to the cell 12. In other words, the AF 41 may request the 5GC 30 to hand over the UE 3 to the cell 12 via the AF request.
[0041] In some implementations, the AF 41 may include in the AF request a cell identifier (e.g., a Physical Cell ID (PCI)) that uniquely identifies the cell 12. The AF 41 may include in the AF request a list of cell identifiers, in which case the 5GC 30 (e.g., the SMF 32) or the RAN 10 (e.g., the RAN node 1) may select one or more specific cells (including the cell 12) from the list of cell identifiers.
[0042] Additionally or alternatively, the AF 41 may include a list of one or more frequency band identifiers (e.g., NR Absolute Radio Frequency Channel Numbers (NR-ARFCNs)) in the AF request. In this case, the 5GC 30 (e.g., SMF 32 or AMF 31) or the RAN 10 (e.g., RAN node 1) may select one or more specific cells (including cell 12) operating in any of the frequency bands included in the list of frequency band identifiers. Additionally or alternatively, the AF 41 may include an Index to RAT / Frequency Selection Priority (RFSP index) in the AF request. The RFSP index is used by the RAN 10 to derive UE-specific cell reselection priorities, for example, to control camping in idle mode. Alternatively, the RFSP index is used by the RAN 10 to decide to redirect a UE in a connected mode (active mode) to a different frequency layer or a different RAT. The RAN 10 may select one or more specific cells (including cell 12) operating in any of the selected frequency bands based on the RFSP index indicated by the AF 41. Additionally or alternatively, the AF 41 may include an Additional Radio Resource Management (RRM) Policy Index (ARPI) in the AF request. The ARPI is used by the RAN 10 to prioritize allocation of RAN resources to UEs.
[0043] The AF request in step 201 may include other information elements. More specifically, the AF request may include an identifier of the UE 3. The identifier of the UE 3 may be a Generic Public Subscription Identifier (GPSI), such as a Mobile Subscriber Integrated Services Digital Network Number (MSISDN) or an external identifier. The AF request may include an identifier of a PDU session (e.g., PDU Session ID). The AF request may include information for identifying one or more QoS flows included in the PDU session (e.g., 5-tuple). The AF request may include a combination of a Data Network Name (DNN) and a Single Network Slice Selection Assistance Information (S-NSSAI). The DNN is an identifier indicating a DN, and indicates a DN (e.g., DN50) to which the traffic of the UE 3 should be routed. The S-NSSAI is an identifier of a network slice. The AF request may include a list of one or more DN Access Identifiers (DNAIs). The DNAI(s) indicate an access location to a DN.
[0044] One or both of the 5GC 30 (e.g., PCF 34, SMF 32, AMF 31) and the RAN 10 (e.g., RAN node 1) may manage the PCI, the list of NR-ARFCNs, the RFSP index, and the ARPI set in the AF request for each UE, each PDU session, each S-NSSAI, each QoS Flow Identifier (QFI), each DN, or each DNN (each APN). When the AMF 31 receives and holds the RFSP index (and ARPI) from the UDM, for example, the AMF 31 may use the RFSP index and ARPI designated by the AF 41 only when handling a specific PDU session, a specific S-NSSAI, a specific QFI, a specific DN, or a specific DNN (specific APN) designated by the AF 41. Similarly, when the RAN 10 receives and retains the RFSP index (and ARPI) from the UDM, the RAN 10 may use the RFSP index (and ARPI) specified by the AF 41 only when handling a specific PDU session, a specific S-NSSAI, a specific QFI, a specific DN, or a specific DNN (specific APN) specified by the AF 41, for example.
[0045] In some implementations, the AF 41 may receive a report from the UE 3 via communication at the application layer and determine whether a particular cell (e.g., cell 12) is available to the UE 3 based on the report. The report from the UE 3 may include one or any combination of the following: a current location of the UE 3, a list of cells measured or detected by the UE 3, and a measurement result of radio quality of each of the one or more cells. The radio quality may be, for example, Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ). Then, in response to determining that the particular cell (e.g., cell 12) is available to the UE 3, the AF 41 may transmit the AF request of step 201. Such an operation can prevent sending an AF request to the 5GC 30 that is unlikely to be successful.
[0046] In response to receiving the AF request, the 5GC 30 sends an N2 request to the RAN node 1 in the RAN 10. More specifically, the PCF 34 receives the AF request directly or via the NEF 35, makes a policy decision based on the AF request, and determines that updated or new Session Management (SM) policy information needs to be sent to the SMF 32. The updated or new SM policy information may include the PCI(s), NR-ARFCN(s), RFSP index, or ARPI sent from the AF 41. The PCF 34 then provides the updated or new SM policy information to the SMF 32. The PCF 34 may issue an Npcf_SMPolicyControl_UpdateNotify request with the updated or new SM policy information.
[0047] The SMF 32 receives updated or generated SM policy information from the PCF 34 based on the AF request. The SMF 32 may interact with the UPF 33 to change the UP path of one or more QoS flows belonging to the established PDU session of the UE 3. For example, the SMF 32 may decide to use a split PDU session, request the UPF 33 to set up a new N3 tunnel to route the existing or additional QoS flows to the RAN node 2, and provide the UPF 33 with new packet detection and forwarding rules. Additionally or alternatively, the SMF 32 may decide to insert a UL CL UPF and an additional PSA UPF into the UP path of the established PDU session of the UE 3. In this case, the SMF 32 may provide the UPF 33 with the N9 tunnel configuration for the insertion of the UL CL UPF and the additional PSA UPF, and the packet detection and forwarding rules.
[0048] In step 202, the 5GC 30 sends an N2 request to the RAN node 1. The N2 request may be a PDU SESSION RESOURCE MODIFY REQUEST message. The N2 request includes any or any combination of a cell identifier, a frequency band identifier, an RFSP index, and an ARPI of the cell 12. The N2 request thereby requests the RAN node 1 to set up or modify a user plane path such that user data belonging to a PDU session for the UE 3 is forwarded via a UP path including a radio connection of the cell 12. In some implementations, the N2 request may request the RAN node 1 to add the cell 12 as an SCG cell of the DC for the UE 3.
[0049] More specifically, the SMF 32 invokes Namf_Communication_N1N2MessageTransfer and sends the N2 SM information and the N1 SM container to the AMF 31. The N1 SM container includes the PDU Session Modification Command message sent to the UE 3. Meanwhile, the N2 SM information includes information required for routing of the QoS flow to be added or updated (e.g. PDU Session ID, QoS Flow Identifier(s) (QFI(s)), and QoS Profile(s), CN Tunnel Info). The CN Tunnel Info indicates the N3 (GTP-U) tunnel endpoint of the UPF 33. The N2 SM information may further include the PCI(s), NR-ARFCN(s), RFSP index, or ARPI sent from the AF 41. As mentioned above, the SMF 32 may receive a list of PCIs or a list of NR-ARFCNs. In this case, SMF 32 may select one PCI or NR-ARFCN from the list and include the selected one in the N2 SM information. The N2 SM information may explicitly indicate that dual connectivity or handover is required. Alternatively, SMF 32 may include a cause in Namf_Communication_N1N2MessageTransfer indicating that dual connectivity or handover is required.
[0050] The RAN node 1 receives the N2 request from the AMF 31 and decides to add the cell 12 as an SCG cell of the DC for the UE 3 or to handover the UE 3 to the cell 12. In step 203, the RAN node 1 may cause the UE 3, which is Radio Resource Control (RRC)_CONNETED, to perform inter-frequency measurement. The RAN node 1 may create a configuration for inter-frequency measurement to enable the UE 3 to measure the frequency band in which the cell 12 operates. More specifically, the RAN node 1 may create a configuration (e.g., measurement gap) required to measure the frequency band in which the cell 12 operates (e.g., FR2 band) taking into account the radio capability of the UE 3 (e.g., the number of Radio Frequency (RF) chains of the UE 3). The RAN node 1 may send an RRC message including the created configuration for inter-frequency measurement to the UE 3. The RRC message may be an RRC Reconfiguration message. Note that if the RAN node 1 has already received the measurement result by the UE 3, the measurement in step 203 may be skipped.
[0051] In step 204, the RAN node 1 performs a Secondary Node (SN) addition procedure to add the cell 12 as a secondary cell (SCG cell). More specifically, the RAN node 1 sends an SN Addition Request message to the RAN node 2. The RAN node 2 sends an SN Addition Request Acknowledge message to the RAN node 1. The SN Addition Request Acknowledge message includes an SN RRC message. Then, the RAN node 1 sends a Master Node (MN) RRC Reconfiguration message to the UE 3. The MN RRC Reconfiguration message includes the SN RRC message received from the RAN node 2 and includes an N1 SM container (PDU Session Modification Command) received from the AMF 31.
[0052] Thereafter, for the radio bearers of cell 12, RAN node 1 (or RAN node 2) updates the UP path with 5GC (UPF 33) via a PDU Session Path Update procedure. Specifically, in step 205, RAN node 1 sends an N2 response to AMF 31. The N2 response may be a PDU SESSION RESOURCE MODIFY RESPONSE message. The N2 response includes N2 SM information. The N2 SM information includes AN Tunnel Info, which indicates the N3 (GTP-U) tunnel endpoint of RAN node 2, which is the SN of the DC. In step 206, AMF 31 forwards the N2 SM information received from RAN node 1 to SMF 32, which updates UPF 33 based on the N2 SM information. This allows UE 3 to perform DC using cell 11 as a Master Cell Group (MCG) cell and cell 12 as a SCG cell.
[0053] Alternatively, in step 204, if the cell 12 is available at the location of the UE 3, the RAN node 1 may initiate a handover procedure to move the UE 3 to the cell 12. More specifically, the RAN node 1 sends a Handover Request message to the RAN node 2. The RAN node 2 sends a Handover Request Acknowledge message to the RAN node 1. The Handover Request Acknowledge message contains a transparent container (i.e., a Handover Command message) to be sent to the UE 3. The RAN node 1 forwards the Handover Command message to the UE 3. In steps 205 and 206, after the handover of the UE 3 is completed, the RAN node 2 (or the RAN node 1) updates the UP path with the 5GC (User Plane Function (UPF)) via a PDU Session Path Update procedure for the radio bearers of the cell 12. This allows the UE 3 to communicate with the DN 50 via the UP path including the radio connection of the cell 12.
[0054] Next, a specific example of UP path change will be described below with reference to Figures 3A to 3E. In the example shown in Figures 3A to 3E, cell 11 may operate in FR1 band (sub-6 GHz) and cell 12 may operate in FR2 band (e.g., 28 GHz). Figure 3A shows an UP path before a change in UP path involving dual connectivity or handover is performed. The UP path 301 shown in Figure 3A is used for the transfer of all QoS flows belonging to a PDU session between DN 50 and UE 3. The UP path 301 includes a radio connection (DRB) of cell 11 as well as an N3 tunnel between RAN node 1 and UPF 33.
[0055] Figure 3B shows the UP path after dual connectivity is started using cell 11 as the MCG cell and cell 12 as the SCG cell. The UP path 311 shown in Figure 3B is the same as the UP path 301 in Figure 3A, and is used for the transfer of one or more QoS flows that have been set up before DC. Meanwhile, the UP path 312 is used for one or more newly added QoS flows that belong to the PDU session between the DN 50 and the UE 3. The UP path 312 includes the radio connection (DRB) of the SCG cell 12 and the N3 tunnel between the RAN node 2 and the UPF 33.
[0056] FIG. 3C also shows the UP path after dual connectivity is started, but in FIG. 3C, a local UPF 33B is inserted. The local UPF 33B operates as a UL CL and an additional PSA. This allows the local UPF 33B to forward uplink traffic of one or more newly added QoS flows to the DN 50B for local access via the UP path 322. Furthermore, the local UPF 33B can forward uplink traffic of one or more QoS flows configured before DC to the DN 50A via the central UPF 33A via the UP path 321. The DN 50A and the DN 50B are the same DN. Furthermore, the PDU session is split in the local UPF 33B. The local UPF 33B forwards downlink traffic of one or more QoS flows configured before DC to the RAN node 1 (MN) and forwards downlink traffic of one or more newly added QoS flows to the RAN node 2 (SN).
[0057] 3D shows the UP path after UE3 is handed over from cell 11 to cell 12. The UP path 331 shown in FIG. 3D is used for one or more QoS flows already set up before DC, and is also used for one or more newly added QoS flows. The UP path 331 includes the radio connection (DRB) of cell 12, as well as the N3 tunnel between RAN node 2 and UPF 33.
[0058] FIG. 3E also shows the UP path after the handover is completed, but in FIG. 3E, a local UPF 33B is inserted. The local UPF 33B in FIG. 3E acts as a UL CL and an additional PSA. This allows the local UPF 33B to forward uplink traffic of one or more newly added QoS flows to the DN 50B for local access via the UP path 342. In addition, the local UPF 33B can forward uplink traffic of one or more QoS flows configured before DC to the DN 50A via the central UPF 33A via the UP path 341. The DN 50A and the DN 50B are the same DN. The local UPF 33B merges downlink traffic of all QoS flows of the PDU session of the UE 3 onto the N3 tunnel (common to the UP paths 341 and 342) between the local UPF 33B and the RAN node 2.
[0059] FIG. 4 illustrates an example of the operation of the AF 41. In step 401, the AF 41 receives a report from the UE 3 via communication at the application layer, and determines whether a particular cell (e.g., cell 12) is available to the UE 3 based on the report. The report from the UE 3 may indicate location information of the UE 3 (e.g., Global Positioning System (GPS) location information) obtained by the UE 3. Additionally or alternatively, the report from the UE 3 may include a list of cells measured or detected by the UE 3. The list may indicate a cell identifier for each detected cell, and may indicate the frequency band in which each cell operates. Additionally or alternatively, the report from the UE 3 may include measurement results of radio quality (e.g., RSRP or RSRQ) of one or more cells. Additionally or alternatively, the report from the UE 3 may include a cell identifier representing a serving cell to which the UE 3 is currently connected (in communication). Additionally or alternatively, the report from the UE 3 may indicate UE radio capability. The UE's radio capabilities can be used to know the NR frequency bands that the UE supports and can be used to know whether the UE supports DC.
[0060] In response to the determination of step 401, the AF 41 requests the 5GC 30 to set up or modify an UP path such that user data belonging to a PDU session for the UE 3 is forwarded via an UP path that includes a radio connection of a particular cell.
[0061] As can be understood from the above description, the signaling described in this embodiment enables the wireless communication network (5GC30 and RAN10) to provide the UE3 with a UP path including a wireless connection of a specific cell (e.g., FR2 cell, cell 12) based on a request from the AF41.
[0062] <Second embodiment> A configuration example of the wireless communication network according to this embodiment is the same as the example described with reference to Fig. 1. This embodiment provides a specific example of the operations of the UE 3, the AF 41, and the 5GC 30.
[0063] Fig. 5 shows an example of signaling according to this embodiment. In step 501, the AF 41 receives a report from the UE 3 via application layer communication. The report includes identities (e.g., PCIs) of one or more cells detected by the UE 3. The report further includes radio quality measurements (e.g., RSRP or RSRQ) of these cells. The report may include frequency band identifiers (e.g., NR-ARFCNs) of one or more cells detected by the UE 3. Note that if the AF 41 has pre-specified the frequency bands to be measured by the UE 3, the report may not include the frequency band identifiers of the detected cells.
[0064] In step 502, the AF 41 requests the 5GC 30 to modify the established PDU session for the UE 3 based on the report from the UE 3 so that the user data belonging to the established PDU session for the UE 3 is forwarded via a UP path including a radio connection of a specific cell (e.g., cell 12). In other words, the AF 41 requests the 5GC 30 to perform dual connectivity for the UE 3 using the specific cell as a SCG cell or a handover of the UE 3 to the specific cell. The AF request sent by the AF 41 in step 502 includes a list of one or more specific cells (a list of cell identifiers (e.g., PCIs)) and further includes measurement results of these specific cells. The AF request may include a list of frequency band identifiers (e.g., NR-ARFCNs) of one or more specific cells. The AF request may include an RFSP index (and an ARPI). Furthermore, the AF request may include other information elements required to request the 5GC 30 to modify the QoS flow of the UE 3. More specifically, the AF request may include an identifier (eg, GPSI) and QoS flow information (eg, 5-tuple) of the UE 3. Additionally, the AF request may include a DNN and an S-NSSAI, or a list of one or more DNAIs.
[0065] According to the signaling in Fig. 5, the SMF 32 or RAN node 1 may take into account the measurement results of the specific cell received from the AF 41 when performing the UP path change based on the AF request. For example, the SMF 32 or RAN node 1 may determine whether to perform dual connectivity or handover for the UP path change based on the received measurement results. For example, the SMF 32 or RAN node 1 may select one specific cell that is preferred for the UE 3 from the list of specific cells based on the received measurement results.
[0066] <Third embodiment> A configuration example of the wireless communication network according to this embodiment is the same as the example described with reference to Fig. 1. This embodiment provides a specific example of the operations of the UE 3, the AF 41, and the 5GC 30.
[0067] FIG. 6 shows an example of signaling according to this embodiment. In step 601, the AF 41 receives a report from the UE 3 via communication at the application layer. The report includes identifiers (e.g., PCIs) of one or more cells detected by the UE 3. The report further includes information indicating a current location of the UE 3. The information may be GPS location information or a cell identifier indicating a serving cell to which the UE 3 is currently connected (in communication). The report may include frequency band identifiers (e.g., NR-ARFCNs) of one or more cells detected by the UE 3. Note that if the AF 41 has previously specified a frequency band to be measured by the UE 3, the report may not include the frequency band identifiers of the detected cells.
[0068] In step 602, the AF 41 requests the 5GC 30 to modify the established PDU session for the UE 3 based on the report from the UE 3 so that the user data belonging to the established PDU session for the UE 3 is forwarded via a UP path including a radio connection of a specific cell (e.g., cell 12). In other words, the AF 41 requests the 5GC 30 to perform dual connectivity for the UE 3 using the specific cell as an SCG cell or a handover of the UE 3 to the specific cell. The AF request sent by the AF 41 in step 602 includes a list of one or more specific cells (a list of cell identifiers (e.g., PCIs)) and further includes information indicating the current location of the UE 3. The AF request may include a list of frequency band identifiers (e.g., NR-ARFCNs) of one or more specific cells. The AF request may include an RFSP index (and an ARPI). In addition, the AF request may include other information elements required to request the 5GC 30 to modify the QoS flow of the UE 3. More specifically, the AF request may include an identifier (eg, GPSI) and QoS flow information (eg, 5-tuple) of the UE 3. Additionally, the AF request may include a DNN and an S-NSSAI, or a list of one or more DNAIs.
[0069] According to the signaling in Figure 6, the SMF 32 or RAN node 1 can take into account the current location of the UE 3 when performing a UP path change based on the AF request. For example, the SMF 32 or RAN node 1 may determine whether to perform dual connectivity or handover for a UP path change based on the current location of the UE 3. For example, the SMF 32 or RAN node 1 may select one specific cell that is preferred for the UE 3 from a list of specific cells based on the current location of the UE 3.
[0070] <Fourth embodiment> The configuration example of the wireless communication network according to this embodiment is the same as the example described with reference to Fig. 1. This embodiment provides a specific example of the operations of the UE 3, the RAN 10, the 5GC 30, and the AF 41.
[0071] FIG. 7 shows an example of signaling for initiating dual connectivity based on a request from AF 41. In step 701, AF 41 communicates with one or more applications 700 (UE applications) running on UE 3. For example, AF 41 may communicate with UE application 700 via an application layer over a PDU session between DN 50 and UE 3. AF 41 may receive a request for a specific service (e.g., large content delivery, online gaming) from UE application 700. AF 41 may receive from UE application 700 a list of one or more specific cells, a list of frequency bands in which these specific cells are operating, measurements of these specific cells by UE 3, or the current location of UE 3, or any combination thereof.
[0072] In steps 702A and 703, the AF 41 sends an AF request to the PCF 34 via the NEF 35. In step 702A, the AF 41 may invoke Npcf_SMPolicyControl_Update to send the AF request to the NEF 35. In step 703, the NEF 35 may invoke Npcf_SMPolicyControl_Update to forward the AF request to the PCF 34.
[0073] Instead of steps 702A and 703, the AF 41 may perform step 702B, that is, the AF 41 may directly send the AF request to the PCF 34. In step 702B, the AF 41 may perform Npcf_SMPolicyControl_Update to send the AF request to the PCF 34.
[0074] In step 704, the PCF 34 generates updated or new SM policy information based on the AF request and provides it to the SMF 32. The PCF 34 may implement an Npcf_SMPolicyControl_UpdateNotify request to send the updated or new SM policy information to the SMF 32.
[0075] The SMF 32 generates N2 SM information and N1 SM container based on the updated or new SM policy information. The N1 SM container includes the PDU Session Modification Command to be sent to the UE 3. Meanwhile, the N2 SM information includes information required for routing of the QoS flow to be added or updated (e.g. PDU Session ID, QoS Flow Identifier(s) (QFI(s)), and QoS Profile(s), CN Tunnel Info). The SMF 32 may interact with the UPF 33 to modify the UP path of one or more QoS flows belonging to the established PDU session of the UE 3. In step 705, the SMF 32 sends the N2 SM information and the N1 SM container to the AMF 31 for forwarding them to the RAN 10. The SMF 32 may perform Namf_Communication_N1N2MessageTransfer.
[0076] In step 706, the AMF 31 generates an N2 request containing the N2 SM information and the N1 SM container received from the SMF 32, and sends it to the RAN 10 (i.e., RAN Node 1). The N2 request may be a PDU SESSION RESOURCE MODIFY REQUEST message.
[0077] The messages of steps 702A (or 702B), 703, 704, 705 and 706 may indicate any or any combination of the PCI, the list of NR-ARFCNs, the RFSP index and the ARPI, which are associated with the UE application 700. This allows the RAN 10 to be provided with RAN related information included in the AF request from the AF 41.
[0078] Steps 707 and 708 are similar to steps 203 and 204 in Fig. 2. In the example of Fig. 7, the RAN node 1 receives an N2 request from the AMF 31 and decides to add the cell 12 as an SCG cell of the DC for the UE 3. In step 707, the RAN node 1 may cause the UE 3, which is Radio Resource Control (RRC)_CONNETED, to perform inter-frequency measurements. If the RAN node 1 has already received the measurement results by the UE 3, the measurement in step 707 may be skipped. In step 708, the RAN node 1 communicates with the RAN node 2 and performs a Secondary Node (SN) addition procedure to add the cell 12 as a secondary cell (SCG cell).
[0079] In step 709, the RAN node 1 sends an MN RRC Reconfiguration message to the UE 3. The MN RRC Reconfiguration message contains the SN RRC message received from the RAN node 2 and contains an N1 SM container (PDU Session Modification Command) received from the AMF 31.
[0080] In step 710, the RAN node 1 sends an N2 response to the AMF 31. The N2 response may be a PDU SESSION RESOURCE MODIFY RESPONSE message. The N2 response includes N2 SM information. The N2 SM information includes AN Tunnel Info, which indicates the N3 (GTP-U) tunnel endpoint of the RAN node 2, which is the SN of the DC.
[0081] In step 711, the AMF 31 forwards the N2 SM information received from the RAN node 1 to the SMF 32, and the SMF 32 updates the UPF 33 based on the N2 SM information. The AMF 31 may perform an Nsmf_PDUSession_UpdateSMContext Request.
[0082] In step 712, the UE3 sends an MN RRC Reconfiguration Complete message to the RAN node 1. The MN RRC Reconfiguration Complete message contains an SN RRC response message for the SN and further contains a NAS message. The RAN node 1 (MN) informs the RAN node 2 (SN) that the reconfiguration procedure of the UE3 has been successfully completed via the SN Reconfiguration Complete message containing the SN RRC response message.
[0083] In step 713, the RAN node 1 forwards the NAS message received from the UE 3 to the AMF 31. The NAS message includes a PDU Session ID and an N1 SM container (PDU Session Modification Command Ack). The N2 message in step 713 may be an UPLINK NAS TRANSPORT message.
[0084] In step 714, the AMF 31 forwards the N1 SM container (PDU Session Modification Command Ack) to the SMF 32. The AMF 31 may perform Nsmf_PDUSession_UpdateSMContext.
[0085] Steps 712 to 714 may be performed before steps 710 and 711.
[0086] In step 715, the SMF 32 sends a response to the request for updated or new SM policy information in step 704 to the PCF 34. The SMF 32 may implement an Npcf_SMPolicyControl_UpdateNotify response.
[0087] <Fifth embodiment> The configuration example of the wireless communication network according to this embodiment is the same as the example described with reference to Fig. 1. This embodiment provides a specific example of the operations of the UE 3, the RAN 10, the 5GC 30, and the AF 41.
[0088] Figure 8 shows an example of signaling for performing handover based on a request from the AF 41. Steps 801 to 808 are similar to steps 701 to 708 in Figure 7. However, in step 808, the RAN node 1 receives an N2 request from the AMF 31 and decides to handover the UE 3 from cell 11 to cell 12. Then, the RAN node 1 communicates with the RAN node 2 and performs a handover preparation procedure.
[0089] In step 809, the source RAN node 1 forwards the Handover Command message received from the target RAN node 2 to the UE 3.
[0090] In step 810, the RAN node 1 or RAN node 2 sends an N2 response to the AMF 31. The N2 response may be a PDU SESSION RESOURCE MODIFY RESPONSE message. The N2 response includes N2 SM information. The N2 SM information includes AN Tunnel Info indicating the N3 (GTP-U) tunnel endpoint of the RAN node 2 serving the target cell 12.
[0091] In step 811, the AMF 31 forwards the N2 SM information received from the RAN node 1 to the SMF 32, and the SMF 32 updates the UPF 33 based on the N2 SM information.
[0092] In step 812, the UE 3 accesses the RAN node 2 via the target cell 12 and sends a NAS message, which includes a PDU Session ID and an N1 SM container (PDU Session Modification Command Ack).
[0093] In step 713, the RAN node 2 forwards the NAS message received from the UE 3 to the AMF 31. The NAS message includes a PDU Session ID and an N1 SM container (PDU Session Modification Command Ack). The N2 message in step 713 may be an UPLINK NAS TRANSPORT message.
[0094] In step 814, the AMF 31 forwards the N1 SM container (PDU Session Modification Command Ack) to the SMF 32. The AMF 31 may perform Nsmf_PDUSession_UpdateSMContext.
[0095] Steps 812 to 814 may be performed before steps 810 and 711.
[0096] In step 815, the SMF 32 sends a response to the request for updated or new SM policy information in step 804 to the PCF 34. The SMF 32 may implement an Npcf_SMPolicyControl_UpdateNotify response.
[0097] Next, configuration examples of the RAN node 1, the RAN node 2, the UE 3, the control plane node (eg, SMF 32) in the 5GC 30, and the AF 41 according to the above-mentioned embodiments will be described below. FIG. 9 is a block diagram showing a configuration example of the RAN node 1 according to the above-mentioned embodiments. The RAN node 2 may have a similar configuration to that shown in FIG. 9. Referring to FIG. 9, the RAN node 1 includes a Radio Frequency (RF) transceiver 901, a network interface 903, a processor 904, and a memory 905. The RF transceiver 901 performs analog RF signal processing to communicate with UEs. The RF transceiver 901 may include multiple transceivers. The RF transceiver 901 is coupled to an antenna array 902 and a processor 904. The RF transceiver 901 receives modulation symbol data from the processor 904, generates a transmit RF signal, and provides the transmit RF signal to the antenna array 902. The RF transceiver 901 also generates a baseband receive signal based on the receive RF signal received by the antenna array 902 and supplies the baseband receive signal to the processor 904. The RF transceiver 901 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.
[0098] The network interface 903 is used to communicate with network nodes (eg, other RAN nodes, the AMF 31, and the UPF 33). The network interface 903 may include, for example, a network interface card (NIC) that complies with the IEEE 802.3 series.
[0099] The processor 904 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. The processor 904 may include multiple processors. For example, the processor 904 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing.
[0100] For example, digital baseband signal processing by the processor 904 may include signal processing of a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. Also, control plane processing by the processor 904 may include processing of Non-Access Stratum (NAS) messages, RRC messages, MAC CEs, and DCIs.
[0101] The processor 904 may include a digital beamformer module for beamforming, which may include a Multiple Input Multiple Output (MIMO) encoder and a precoder.
[0102] The memory 905 is configured by a combination of volatile memory and non-volatile memory. The volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is, for example, Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof. The memory 905 may include storage located remotely from the processor 904. In this case, the processor 904 may access the memory 905 via the network interface 903 or an I / O interface not shown.
[0103] The memory 905 may store one or more software modules (computer programs) 906 including instructions and data for performing the processes of the RAN node 1 described in the above embodiments. In some implementations, the processor 904 may be configured to read the software modules 906 from the memory 905 and execute them to perform the processes of the RAN node 1 described in the above embodiments.
[0104] In addition, when the RAN node 1 is a Central Unit (eg, gNB-CU) in a C-RAN deployment, the RAN node 1 does not need to include an RF transceiver 901 (and an antenna array 902).
[0105] FIG. 10 is a block diagram showing a configuration example of the UE 3. The Radio Frequency (RF) transceiver 1001 performs analog RF signal processing to communicate with NG-RAN nodes. The RF transceiver 1001 may include multiple transceivers. The analog RF signal processing performed by the RF transceiver 1001 includes frequency up-conversion, frequency down-conversion, and amplification. The RF transceiver 1001 is coupled to the antenna array 1002 and the baseband processor 1003. The RF transceiver 1001 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1003, generates a transmit RF signal, and provides the transmit RF signal to the antenna array 1002. The RF transceiver 1001 also generates a baseband receive signal based on the receive RF signal received by the antenna array 1002, and provides the baseband receive signal to the baseband processor 1003. The RF transceiver 1001 may include an analog beamformer circuit for beamforming. The analog beamformer circuitry includes, for example, multiple phase shifters and multiple power amplifiers.
[0106] The baseband processor 1003 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) generation / decomposition of transmission format (transmission frame), (d) transmission line coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). Meanwhile, control plane processing includes communication management of layer 1 (e.g., transmission power control), layer 2 (e.g., radio resource management, and hybrid automatic repeat request (HARQ) processing), and layer 3 (e.g., signaling related to attachment, mobility, and call management).
[0107] For example, the digital baseband signal processing by the baseband processor 1003 may include signal processing of a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. Also, the control plane processing by the baseband processor 1003 may include processing of a Non-Access Stratum (NAS) protocol, a Radio Resource Control (RRC) protocol, and MAC Control Elements (CEs).
[0108] The baseband processor 1003 may perform Multiple Input Multiple Output (MIMO) encoding and precoding for beamforming.
[0109] The baseband processor 1003 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing. In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 1004 described later.
[0110] The application processor 1004 is also called a CPU, an MPU, a microprocessor, or a processor core. The application processor 1004 may include multiple processors (multiple processor cores). The application processor 1004 executes a system software program (operating system (OS)) and various application programs (e.g., a calling application, a web browser, a mailer, a camera operation application, and a music playback application) read from the memory 1006 or a memory not shown, thereby implementing various functions of the UE3.
[0111] In some implementations, the baseband processor 1003 and the application processor 1004 may be integrated on a single chip, as shown by the dashed line (1005) in Figure 10. In other words, the baseband processor 1003 and the application processor 1004 may be implemented as a single System on Chip (SoC) device 1005. An SoC device may also be called a system Large Scale Integration (LSI) or a chipset.
[0112] The memory 1006 is a volatile memory or a non-volatile memory, or a combination thereof. The memory 1006 may include a plurality of physically independent memory devices. The volatile memory is, for example, a Static Random Access Memory (SRAM) or a Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is a Mask Read Only Memory (MROM), an Electrically Erasable Programmable ROM (EEPROM), a flash memory, or a hard disk drive, or any combination thereof. For example, the memory 1006 may include an external memory device accessible from the baseband processor 1003, the application processor 1004, and the SoC 1005. The memory 1006 may include an internal memory device integrated in the baseband processor 1003, the application processor 1004, or the SoC 1005. Furthermore, the memory 1006 may include a memory in a Universal Integrated Circuit Card (UICC).
[0113] The memory 1006 may store one or more software modules (computer programs) 1007 including instructions and data for performing processing by the UE 3 described in the above-mentioned embodiments. In some implementations, the baseband processor 1003 or the application processor 1004 may be configured to read the software module 1007 from the memory 1006 and execute it to perform processing by the UE 3 described in the above-mentioned embodiments using the drawings.
[0114] In addition, the control plane processing and operations performed by UE3 described in the above embodiment can be realized by elements other than the RF transceiver 1001 and the antenna array 1002, i.e., at least one of the baseband processor 1003 and the application processor 1004, and the memory 1006 storing the software module 1007.
[0115] FIG. 11 shows an example of the configuration of the AF 41. The control plane nodes (eg, AMF 31, SMF 32, PCF 34, and NEF 35) in the 5GC 30 may also have a similar configuration as shown in FIG. 11. Referring to FIG. 11, the AF 41 includes a network interface 1101, a processor 1102, and a memory 1103. The network interface 1101 is used, for example, to communicate with the DN 50 and to communicate with network functions (NFs) or nodes in the 5GC. Other NFs or nodes in the 5GC include, for example, UDM, AUSF, SMF, and PCF. The network interface 1101 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series.
[0116] The processor 1102 may be, for example, a microprocessor, a Micro Processing Unit (MPU), or a Central Processing Unit (CPU). The processor 1102 may include multiple processors.
[0117] The memory 1103 is composed of a volatile memory and a non-volatile memory. The memory 1103 may include a plurality of physically independent memory devices. The volatile memory is, for example, a static random access memory (SRAM) or a dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is, for example, a mask read only memory (MROM), an electrically erasable programmable ROM (EEPROM), a flash memory, or a hard disk drive, or any combination thereof. The memory 1103 may include a storage located away from the processor 1102. In this case, the processor 1102 may access the memory 1103 via the network interface 1101 or an I / O interface not shown.
[0118] The memory 1103 may store one or more software modules (computer programs) 1104 including instructions and data for performing processing by the AF 41 described in the above-described embodiments. In some implementations, the processor 1102 may be configured to read the software modules 1104 from the memory 1103 and execute them to perform processing by the AF 41 described in the above-described embodiments.
[0119] As described with reference to FIG. 9, FIG. 10, and FIG. 11, each of the processors of the RAN node 1, the RAN node 2, the control plane node (e.g., SMF 32) in the 5GC 30, and the AF 41 according to the above-mentioned embodiment executes one or more programs including instructions for causing a computer to execute the algorithm described with reference to the drawings. The programs can be stored and provided to a computer using various types of non-transitory computer readable media. The non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include magnetic storage media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical storage media (e.g., magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM, programmable ROM (PROM), erasable PROM (EPROM), flash ROM, random access memory (RAM)). The program may be provided to the computer by various types of transitory computer readable media. Examples of the transitory computer readable medium include an electric signal, an optical signal, and an electromagnetic wave. The transitory computer readable medium may provide the program to the computer via a wired communication path such as an electric wire and an optical fiber, or via a wireless communication path.
[0120] <Other embodiments> The above-described embodiments may be implemented independently of each other, or the whole or part of the embodiments may be implemented in appropriate combination.
[0121] Furthermore, the above-described embodiment is merely an example of application of the technical idea obtained by the inventor of the present invention. In other words, the technical idea is not limited to the above-described embodiment, and various modifications are possible. [Explanation of symbols]
[0122] 1 RAN node 2. RAN Node 3. UE 10 RAN 11, 12 Cells 30 5GC 31 AMF 32 SMF 33, 33A, 33B UPF 34 PCF 35 NEF 41AF 50, 50A, 50B DN 905 Memory 906 Modules 1003 Baseband Processor 1004 Application Processor 1007 Modules 1103 Memory 1104 Modules
Claims
1. A means for receiving a request for controlling a policy of a user equipment (UE) from a network exposure function (NEF) device or an application function (AF) device; means for making a policy decision based on receipt of the request; the request comprises information identifying a Radio Access Technology (RAT) frequency selection priority; PCF (Policy Control Function) device.
2. A means for transmitting a request for controlling a policy of a UE (user equipment) to a PCF (Policy Control Function) device or a NEF (Network Exposure Function) device, the request comprises information identifying a Radio Access Technology (RAT) frequency selection priority; The request triggers a policy decision in the PCF device. Application Function (AF) device.
3. A means for transmitting a request for controlling a policy of a user equipment (UE) to a policy control function (PCF) device, the request comprises information identifying a Radio Access Technology (RAT) frequency selection priority; The request triggers a policy decision in the PCF device. NEF (Network Exposure Function) device.
4. Receive a request for controlling a policy of a user equipment (UE) from a network exposure function (NEF) device or an application function (AF) device; making a policy decision based on receiving the request; the request comprises information identifying a Radio Access Technology (RAT) frequency selection priority; A method for a PCF (Policy Control Function) device.
5. Sending a request to control the policy of UE (user equipment) to a PCF (Policy Control Function) device or NEF (Network Exposure Function) device; the request comprises information identifying a Radio Access Technology (RAT) frequency selection priority; The request triggers a policy decision in the PCF device. Method of Application Function (AF) device.
6. Sends a request to the PCF (Policy Control Function) device to control the policy of the UE (user equipment), the request comprises information identifying a Radio Access Technology (RAT) frequency selection priority; The request triggers a policy decision in the PCF device. A method for the Network Exposure Function (NEF) device.
Citation Information
Patent Citations
Mobile communication system, radio station, mobile communication control method, and nontemporary computer-readable medium in which mobile communication control program has been stored
WO2014013646A1
Dynamic rsfp
WO2019243872A1
