Establishment of Protocol Data Unit Session

Abstract

To provide a method for establishing a protocol data unit (PDU) session in a wireless communication system, as well as related wireless devices, network nodes, and programs.SOLUTION: A method executed by a core network node in a core network of a wireless communication system includes: receiving a first request to establish a first PDU session between user equipment (UE) and a user plane function in the core network (1102); generating user plane (UP) security enforcement information to be applied to the first PDU session (1104); transmitting the UP security enforcement information to a radio access network (RAN) node to establish the first PDU session (1106); and storing the UP security enforcement information for use in establishing a subsequent PDU session for the UE (1108).SELECTED DRAWING: Figure 11A

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication systems, and more specifically, to establishing protocol data unit sessions in a wireless communication system, and to related wireless devices, network nodes, computer programs, and computer program products.

Background Art

[0002] Figure 1A depicts a simplified wireless communication system. The system includes a UE 100 that communicates with one or more access nodes 210, 220 using wireless connections 107, 108. The access nodes 210, 220 are connected to a core network node 106. The access nodes 210 - 220 are part of a radio access network 105.

[0003] For a wireless communication system compliant with the 3GPP evolved packet system (EPS) standard, the access nodes 210, 220 typically correspond to evolved Node Bs (eNBs), and the core network node 106 typically corresponds to either a mobility management entity (MME) and / or a serving gateway (SGW). The eNB is part of a radio access network (RAN) 105, which in this case is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), while the MME and SGW are both part of an Evolved Packet Core (EPC) network.

[0004] For a wireless communication system compliant with the 3GPP 5G system (5GS) standard, the access nodes 210, 220 typically correspond to 5G Node B (gNB), and the core network node 106 typically corresponds to either the Access and Mobility Management Function (AMF) and / or the User Plane Function (UPF). The gNB is part of the radio access network 105, which is the NG-RAN (Next Generation Radio Access Network) in this case, while the AMF and UPF are both part of the 5GC (5G Core Network).

[0005] 5G is expected to support many new scenarios and use cases and to become an enabler for the Internet of Things (IoT). The NG system is expected to provide connectivity to a wide range of new devices such as sensors, smart wearables, vehicles, machines, etc. And flexibility should be an important characteristic of the NG system. This is reflected in the security requirements for network access, which require supporting multiple alternative authentication methods and different types of certificates than the normal AKA certificates securely stored in the UICC pre-configured by the operator. This should enable the factory owner or enterprise to utilize its own identity and certificate management system for authentication and access network security.

[0006] Figure 1B shows an example of a 5G system architecture (see 3GPP TS23.501 [1] for further details). As shown in Figure 1B, multiple functional entities (e.g., AMF, SMF, etc.) are connected via communication links. The Access and Mobility Management Function (AMF) communicates with the radio access network (RAN) and one or more user equipments (UEs), and the Session Management Function (SMF) communicates with the User Plane Function (UPF). This approach to modeling the system is also known as the "service-based architecture".

[0007] The various functions depicted in Figure 1B are described hereinafter.

[0008] The Access and Mobility Management Function (AMF) supports the termination of non-access stratum (NAS signaling), NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management.

[0009] The Session Management Function (SMF) supports session management (session establishment, modification, release), allocation and management of the UE's IP (Internet Protocol) address, DHCP (Dynamic Host Configuration Protocol) function, termination of NAS signaling related to session management, downlink (DL) data notification, and traffic steering configuration for the User Plane Function (UPF) for appropriate traffic routing.

[0010] The User Plane Function (UPF) supports packet routing and forwarding, packet inspection, service quality (QoS) handling, operates as an external PDU (Protocol Data Unit) session point of interconnection to the data network (DN), and is an anchor point for intra- and inter-RAT (Radio Access Technology) mobility.

[0011] The Policy Control Function (PCF) supports a unified policy framework that provides policy rules to the control plane (CP) function and access subscription information for policy decision-making in the Unified Data Repository (UDR).

[0012] The Authentication Server Function (AUSF) operates as an authentication server.

[0013] The Unified Data Management (UDM) supports the generation of authentication and key agreement (AKA) certificates, user identification handling, access authorization, and subscription management.

[0014] The Application Function (AF) supports the action of the application on traffic routing, access to the Network Exposure Function (NEF), and interaction with the policy framework for policy control.

[0015] The NEF supports the exposure of capabilities and events, the secure provision of information from external applications to the 3GPP network, and the conversion of internal / external information.

[0016] The NF Repository Function (NRF) supports the service discovery function and maintains the profiles of network functions (NFs) and available NF instances.

[0017] The Network Slice Selection Function (NSSF) supports the selection of network slice instances to serve the UE, the determination of the allowed Network Slice Selection Assistance Information (NSSAI), and the determination of the set of AMFs to be used to serve the UE.

[0018] For the purpose of boosting the performance of the system, a feature called Dual Connectivity (DC) was incorporated into LTE, which enables the utilization of a base station group (referred to as eNB in LTE) with a non-ideal backhaul. This feature is realized by connecting the base station playing the role of the Master Node (MN) to another base station playing the role of the Secondary Node (SN), and allowing the MN to offload data radio bearers to the SN and utilize the resources of the SN.

[0019] In the context of 5G, a similar feature called Extended Dual Connectivity was incorporated into LTE to enable the use of the new radio (NR), which is a 5G radio technology, as described in Option 3 / 3a in Figure 2. In this feature, the MN is an extended eNB and the SN is a gNB (which is a base station providing NR radio access).

[0020] This feature, called dual connectivity, will also be supported in the 5G system with some extensions. Network architecture options 4 / 4a and 7 / a for dual connectivity in a 5G system involving multiple radio access technologies (RATs) and a 5G core network (CN) are shown in Figure 2.

[0021] Figure 3 shows the so-called EN-DC architecture, in which the EPC core operates with the E-UTRAN network, and the E-UTRAN network includes both eNB and en-gNB.

[0022] In the 5G system, multi-RAT dual connectivity (MR-DC) is a generalization of the intra-E-UTRAN dual connectivity (DC) described above, in which multiple Rx / Tx UEs may be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, one providing E-UTRA access and the other providing NR access. One node operates as the MN and the other as the SN. The MN and SN are connected via a network interface, and at least the MN is connected to the 5GC / NGC. The MN can be either a gNB or an ng-eNB. The SN can be either a gNB or an ng-eNB.

[0023] Figure 4 shows network architecture options 4 / 4a and 7 / a for dual connectivity in the 5G system.

[0024] In MR-DC, the UE has a single Radio Resource Control (RRC) state based on a single C-plane connection towards the MN RRC and the core network. FIG. 5 shows the control plane architecture for MR-DC. Each radio node has its own RRC entity (E-UTRA version if the node is an ng-eNB, NR version if the node is a gNB) that can generate RRC PDUs to be sent to the UE.

[0025] RRC PDUs generated by the SN can be transported to the UE via the MN. The MN always sends the initial SN RRC configuration via the master cell group (MCG) signaling radio bearer SRB (SRB1), but subsequent reconfigurations may be transported via the MN or the SN. When transporting RRC PDUs from the SN, the MN does not modify the UE configuration provided by the SN.

[0026] Among the new security features in the 5G system, there is support for the introduction of user plane (UP) integrity protection and a separate mechanism for UP security negotiation. The term negotiation refers to the procedure for determining whether integrity or confidentiality should be activated for a UP session and which of them should be activated.

[0027] In comparison with LTE, there is no integrity protection for the UP, and the negotiation of the UP confidentiality is integrated into the activation of the security for the control plane (CP) in the access stratum (AS) between the eNB and the UE. As described in TS33.401 [3], the security for the AS CP is activated by the execution of the AS security mode command (SMC) procedure that enables the selection of the encryption algorithm and the activation of the security for the RRC protocol. It should be noted that in fact, a lower-level protocol provides security, specifically the PDCP (Packet Data Convergence Protocol) within the AS CP protocol stack. Furthermore, in LTE, since integrity protection for the UP is not supported and confidentiality protection is essential, the confidentiality algorithm selected during the above-mentioned AS SMC is automatically used for the protection of the UP traffic.

[0028] A new feature for the negotiation of the UP security in the 5G system is that the RAN node can receive the UP security implementation information from the core network (CN) during the PDU session establishment procedure (see TS23.502 [4]). The UP security implementation information provides the user plane security policy for the PDU session to the NG-RAN. For example, the UP security implementation information indicates whether UP integrity protection and / or UP confidentiality protection is required, preferred, or not required. See 3GPP TS23.501 [1]. The UP security implementation information may also provide other information such as the maximum data rate supported for the integrity protection provided by the UE.

[0029] The UP security policies defined in the UP security implementation information are applicable at the PDU session level. That is, the RAN applies the UP security implementation information received from the CN to all data radio bearers (DRBs) serving the PDU session in question. Further, the UP security policy includes security implementation information such as separate indications as to whether integrity protection and / or confidentiality protection should be activated.

[0030] This type of flexibility is necessary in a 5G system that is expected to provide connectivity for a diverse range of service and device types. For IoT services, integrity protection should be sufficient in many cases, while for normal voice and broadcast services, confidentiality protection is required as in LTE.

Summary of the Invention

[0031] The object of the inventive concept is to streamline the establishment of PDU sessions in a wireless communication network. Methods according to some embodiments, which are performed by a core network node in a core network of a wireless communication system, include receiving a first request for establishing a first protocol data unit (PDU) session between a user equipment (UE) and a user plane function within the core network, generating user plane (UP) security implementation information to be applied to the first PDU session, transmitting the UP security implementation information to a radio access network (RAN) node for establishing the first PDU session, and storing the UP security implementation information for use in establishing subsequent PDU sessions for the UE.

[0032] The method may further include receiving a second request for establishing a second PDU session between the UE and the user plane function within the core network.

[0033] The method may further include transmitting the UP security implementation information to the RAN node to establish the second PDU session.

[0034] In some embodiments, storing the UP security implementation information is performed by a session management function (SMF) in the core network.

[0035] The method may further include selecting a user plane function for terminating the second PDU session.

[0036] In some embodiments, the second PDU session is established for redundant data transmission with the first PDU session.

[0037] In some embodiments, the second PDU session is carried on a data radio bearer (DRB) established between the UE and a secondary node.

[0038] In some embodiments, storing the UP security implementation information is performed by the core network.

[0039] In some embodiments, storing the UP security implementation information is performed by a policy control function (PCF) or a unified data management (UDM) function in the core network.

[0040] In some embodiments, the RAN node includes a master node. In some embodiments, the RAN node includes a gNB or an ng-eNB. In some embodiments, the first request is received from the UE.

[0041] Core network nodes according to some embodiments include a processing circuit, a network interface coupled to the processing circuit, and a memory coupled to the processing circuit. The memory includes machine-readable program instructions that, when executed by the processing circuit, cause the network node to receive a first request to establish a first protocol data unit session between a user equipment and a user plane function within the core network, generate user plane security implementation information to be applied to the first PDU session, transmit the UP security implementation information to a radio access network node to establish the first PDU session, and store the UP security implementation information for use in establishing subsequent PDU sessions for the UE.

[0042] Core network nodes according to some embodiments are adapted to receive a first request to establish a first protocol data unit session between a user equipment and a user plane function within the core network, generate user plane security implementation information to be applied to the first PDU session, transmit the UP security implementation information to a radio access network node to establish the first PDU session, and store the UP security implementation information for use in establishing subsequent PDU sessions for the UE.

[0043] Some embodiments provide a computer program comprising program code executed by a processing circuit of a core network (CN) node configured to operate in a communication network, the execution of the program code causing the CN node to receive a first request to establish a first protocol data unit session between a user equipment and a user plane function within the core network, generate user plane security implementation information to be applied to the first PDU session, transmit the UP security implementation information to a radio access network node to establish the first PDU session, and store the UP security implementation information for use in establishing subsequent PDU sessions for the UE.

[0044] Some embodiments provide a computer program product comprising a non-transitory storage medium comprising program code executed by a processing circuit of a core network (CN) node configured to operate in a communication network, the execution of the program code causing the CN node to receive a first request to establish a first protocol data unit session between a user equipment and a user plane function within the core network, generate user plane security implementation information to be applied to the first PDU session, transmit the UP security implementation information to a radio access network node to establish the first PDU session, and store the UP security implementation information for use in establishing subsequent PDU sessions for the UE.

[0045] A method performed by a radio access network node according to some embodiments of a wireless communication system includes receiving a first request to establish a first protocol data unit session between a user equipment connected to the RAN node and a user plane function in the core network; receiving user plane security implementation information to be applied to the first PDU session from a core network node; modifying the UP security implementation information to provide modified UP security implementation information; storing the modified UP security implementation information for use in setting up subsequent PDU sessions for the UE; and establishing the first PDU session using the modified UP security implementation information.

[0046] The method may further include receiving a second request to establish a second protocol data unit session between the UE and the user plane function in the core network; receiving the UP security implementation information from the core network node; and establishing the second PDU session using the modified UP security implementation information.

[0047] The method may further include establishing a dual connectivity (DC) connection between the UE and a secondary node; and allocating the second PDU session to the DC connection.

[0048] The method may further include transmitting the modified UP security implementation information to the secondary node for application to the second PDU session.

[0049] In some embodiments, the second PDU session is carried on a data radio bearer (DRB) established between the UE and the secondary node.

[0050] In some embodiments, the core network node is responsible for the session management function (SMF). In some embodiments, the RAN node includes a gNB or an ng-eNB.

[0051] A radio access network node according to some embodiments includes a processing circuit, a network interface connected to the processing circuit, and a memory connected to the processing circuit. The memory includes machine-readable program instructions that, when executed by the processing circuit, cause the RAN node to receive a first request to establish a first protocol data unit session between a user equipment connected to the RAN node and a user plane function in the core network, receive user plane security implementation information to be applied to the first PDU session from a core network node, modify the UP security implementation information to provide modified UP security implementation information, store the modified UP security implementation information for use in setting up subsequent PDU sessions for the UE, and use the modified UP security implementation information to establish the first PDU session.

[0052] A radio access network node according to some embodiments is adapted to receive a first request to establish a first protocol data unit session between a user equipment connected to the RAN node and a user plane function in the core network, receive user plane security implementation information to be applied to the first PDU session from a core network node, modify the UP security implementation information to provide modified UP security implementation information, store the modified UP security implementation information for use in setting up subsequent PDU sessions for the UE, and use the modified UP security implementation information to establish the first PDU session.

[0053] Some embodiments provide a computer program comprising program code executable by a processing circuit of a radio access network node configured to operate in a communication network, the execution of the program code causing the RAN node to receive a first request to establish a first protocol data unit session between a user equipment connected to the RAN node and a user plane function within the core network, receive user plane security implementation information to be applied to the first PDU session from a core network node, modify the UP security implementation information to provide modified UP security implementation information, store the modified UP security implementation information for use in setting up subsequent PDU sessions for the UE, and establish the first PDU session using the modified UP security implementation information.

[0054] Some embodiments provide a computer program product comprising a non-transitory storage medium comprising program code executable by a processing circuit of a radio access network node configured to operate in a communication network, the execution of the program code causing the RAN node to receive a first request to establish a first protocol data unit session between a user equipment connected to the RAN node and a user plane function within the core network, receive user plane security implementation information to be applied to the first PDU session from a core network node, modify the UP security implementation information to provide modified UP security implementation information, store the modified UP security implementation information for use in setting up subsequent PDU sessions for the UE, and establish the first PDU session using the modified UP security implementation information. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The accompanying drawings, which are incorporated herein to provide a further understanding of the disclosure, illustrate non-limiting embodiments of the inventive concept. The drawings are as follows:

[0056]

Figure 1A

Figure 1B

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11A

Figure 11B

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Mode for Carrying Out the Invention

[0057] Reference will now be made to the accompanying drawings, which illustrate examples of embodiments of the inventive concept, and in which the inventive concept will be more fully described. However, the inventive concept may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. It should be noted that the embodiments are not mutually exclusive. Components from one embodiment may be implicitly assumed to be present or used in other embodiments.

[0058] The following description presents various embodiments of the disclosed subject matter. The embodiments are presented by way of example and are not to be construed as limiting the scope of the disclosed subject matter. For example, some details of the described embodiments may be modified, omitted, or extended without departing from the scope of the described subject matter.

[0059] 3GPP SA2 conducted research on 5G URLLC in Rel-16 in 3GPP TR23.725 [2]. Here, URLLC represents Ultra-Reliable and Low Latency Communication.

[0060] (It may be difficult to achieve using only a single path on the user plane) To ensure high reliability, additional communication paths to / from the UE may be supported in 5GS. Depending on the conditions of the network deployment (e.g., which network function (NF) or segment fails to meet the reliability requirements), additional communication paths may be applied to the user plane path between the UE and the network.

[0061] In SA2 solution #1 proposed in 3GPP TR23.725[2], the UE establishes two PDU sessions with the network. Referring to FIG. 6, one PDU session reaches UPF1 which operates as a PDU session anchor from the UE via the master gNB (MgNB), and the other PDU session reaches UPF2 which operates as a PDU session anchor from the UE via the secondary gNB (SgNB). Based on these two PDU sessions, two independent paths are set up. UPF1 and UPF2 are connected to the same data network (DN), even if the traffic via UPF1 and UPF2 can be routed through different user plane nodes within the DN.

[0062] According to 3GPP TR23.725[2], the setup of the two PDU sessions and the subsequent establishment of disconnection are performed as shown in FIG. 7. The master node (MN) and / or secondary node (SN) in FIG. 7 can be implemented as a gNB or ng-eNB.

[0063] For one PDU session used for redundant data transmission, the core network (e.g., by the SMF within the CN) explicitly requests that the user plane pass through the MN, and for the other (second) PDU session used for redundant data transmission, the core network explicitly requests that the user plane pass through the SN using dual connectivity to the MN. As defined in 3GPP TS37.340[5], the MN sets up dual connectivity so that the session will have an end-to-end redundant path. This implies that all DRBs established for the second PDU session to pass through the SN will be offloaded by the MN to the SN.

[0064] What is important in this scenario is that the same key is not used for the two redundant user planes (for the first and second PDU sessions). Otherwise, if the same key is used for the two redundant user planes, when one path is compromised, the second path will also be compromised. Also, if two different keys are used for the two redundant user planes (for the first and second PDU sessions), the attacker cannot correlate the two data streams.

[0065] According to 3GPP TS23.501 [1], the user plane security policy provides information at the same or equivalent level as the user plane security enforcement information. The user plane security enforcement information is provided to the UE once determined by the SMF at the establishment of the PDU session and applied throughout the lifetime of the PDU session. The user plane security enforcement information provides the user plane security policy for the PDU session to the gNB or ng-eNB within the NG-RAN. It indicates whether the UP integrity protection is as follows:

[0066] Required: Assume that UP integrity protection is applied to all traffic on the PDU session.

[0067] Preferred: UP integrity protection should be applied to all traffic on the PDU session.

[0068] Not Needed: Assume that UP integrity protection is not applied to the PDU session.

[0069] Also, it indicates whether the UP confidentiality protection is as follows:

[0070] Required: Assume that UP confidentiality protection is applied to all traffic on the PDU session.

[0071] Desirable: UP confidentiality protection should be applied to all traffic on the PDU session.

[0072] Not required: Assume that UP confidentiality protection is not applied to the PDU session.

[0073] In the current understanding, in a 5G system, an ng-eNB (a base station that operates as a secondary node (SN) providing LTE radio and connected to the 5G core) will not support user plane integrity protection in 3GPP Release 15.

[0074] This creates potential problems when the capabilities of the SN and MN are different. Consider an example of UP integrity protection. In Option 4 / 4a, which is a network architecture option in 5G for dual connectivity, even if UP integrity protection is activated at the MN, it cannot be activated at the SN. Because in Option 4 / 4a where the gNB operates as the master node (MN), when a user plane security policy that requires UP integrity protection to be activated for all DRBs established for an individual PDU session is received from the 5G core network, the master node (MN) can activate UP integrity protection. However, when the ng-eNB is added as the SN, the UP integrity protection for the bearers within the SN will fail because the ng-eNB does not support UP integrity protection. Another example is Option 7 / 7a where UP integrity protection may be already activated for some bearers within the SN because the SN is a gNB. However, when those bearers are transferred to the MN, the activation of UP integrity protection within the MN will fail because the MN is an ng-eNB.

[0075] The assumption in 5G URLLC Release 16 is that the user plane security policy for the multiple PDU sessions used for redundant data transmission should have the same settings for the activation status for encryption and integrity protection. Otherwise, if an attacker knows that integrity protection is enabled on one path but not on the second path, the attacker may jam on the first path to prevent the user plane data from being transferred from the gNB / ng-eNB to the UPF, and modify the user plane data transmitted on the second path.

[0076] In 3GPP Release 15, in the 5G dual connectivity described in TS33.501 [6], the master node (MN) can modify the settings received from the SMF within the user plane security policy if the settings are set to a value of "preferred" for either or both encryption or integrity protection and the MN cannot comply with the settings received in the user plane security policy.

[0077] When two PDU sessions are established between the UE, with the user plane path for the first PDU session passing through the master node (MN) and the user plane path for the second PDU session passing through the secondary node (SN), there are several potential issues (Issue 1 and Issue 2) with using the above solution for URLLC services.

[0078] Issue 1: Different UP security implementation information (i.e., different security activation for encryption and integrity protection) may be indicated by the SMF to the master node (MN) for the first PDU session and the second PDU session.

[0079] Problem 2: MN may modify the settings in the UP security implementation information received from the SMF for the first PDU session before applying security to the DRB for the first PDU session established between MN and the UE.

[0080] If MN receives UP security implementation information from the SMF for a second PDU session (i.e., the user plane path passing through the SN) and offloads the DRB for the second PDU session to the SN, MN may simply transfer the UP security implementation information received from the SMF, and then the SN needs to comply with the security settings accepted in the UP security implementation information received from MN.

[0081] As a result, the DRBs established between the same UE for the first PDU session and the second PDU session will likely have different security activation settings.

[0082] Some of the embodiments described herein provide a system / method and associated procedures that enable the core network (i.e., the SMF) to handle the UP security implementation information for the first PDU session. Moreover, some of the embodiments described herein provide a system / method and associated procedures that enable the master node to handle the UP security activation status for the DRB established between the UE for the first PDU session.

[0083] According to some embodiments, the system / method described herein may have the following advantages:

[0084] First, using the dual connectivity architecture, the same settings in the UP security implementation information are advantageously provided by the SMF to the same master node (MN) for the first PDU session and the second PDU session used for redundant data transmission.

[0085] Second, the same settings for encryption and integrity protection that are stored in the UP security activation status and applied to the first PDU session at the master node (MN) can be advantageously provided to the secondary node and applied to the second PDU session. This means that the same UP security activation status can be applied to the DRBs for the first PDU session and the second PDU session.

[0086] According to some embodiments, to address the first issue, the UE initiates a PDU establishment procedure with the network for redundant data transmission (such as for supporting URLLC services) for the first PDU session. When the SMF determines the UP security implementation information to be applied to the first PDU session, the UP security implementation information stored by the SMF is provided to the MN and applied to the DRB established for the first PDU session between the MN and the UE.

[0087] When the same UE initiates a PDU establishment procedure with the network for redundant data transmission for the second PDU session, the SMF provides the same stored UP security implementation information (applied to the first PDU session) to the MN. This UP security implementation information is applied to the DRB established for the second PDU session between the SN and the UE.

[0088] Referring to FIG. 8, the UE initiates a registration procedure with the network. In step 1, the UE initiates a PDU establishment procedure with the network for redundant data transmission (URLLC) for the first PDU session. The SMF determines the UP security implementation information to be applied to the first PDU session. At 802, the SMF stores the UP security implementation information before providing it to the MN. The MN then applies the UP security implementation information received from the SMF to the DRB established for the first PDU session between the MN and the UE.

[0089] In step 2, the same UE starts a second PDU establishment procedure with the network for redundant data transmission for the second PDU session. At 804, the SMF reads the stored UP security enforcement information applied to the first PDU session and provides the stored UP security enforcement information to the MN when requesting the second PDU session. At 806, the MN transfers the UP security enforcement information received from the SMF to the SN. The SN applies the UP security enforcement information received from the MN to the DRB established for the second PDU session between the SN and the UE.

[0090] To address the second issue, when the MN receives from the SMF a request to establish a DRB for the first PDU session between the MN and the UE for redundant data transmission, if the security activation setting within the UP security enforcement information received from the SMF for the first PDU session has been modified, the MN stores the applied UP security activation status used for the DRB established between the MN and the UE for the first PDU session.

[0091] When the MN receives from the SMF a request to establish a DRB for the second PDU session between the SN and the UE for redundant data transmission, instead of the UP security enforcement information received from the SMF, the MN provides the stored "UP security activation status" to the SN when offloading it to the DRB for the second PDU session used for redundant data transmission. It is not allowed for the SN to modify the UP security activation status received from the MN. This ensures that the same security settings are applied to the DRBs for the first and second PDU sessions established between the UE.

[0092] Referring to FIG. 9, the UE starts a registration procedure with the network.

[0093] In step 1, the UE starts a PDU establishment procedure with the network for redundant data transmission for the first PDU session. The SMF determines the UP security implementation information to be applied to the first PDU session. The SMF provides the UP security implementation information to the MN. The MN may modify the settings within the received UP security implementation information. In this case, the MN stores, at 902, the modified settings used by the MN when activating security for the DRB for the first PDU session established between the MN and the UE.

[0094] For example, if the UP Integrity Protection, which is a parameter within the received UP security implementation information, is set to the value "preferred", but the MN does not support UP Integrity Protection, the MN may set the UP Integrity Protection as a parameter to "not required". The MN will not activate UP Integrity Protection for the DRB established for the first PDU session between the MN and the UE. However, in this case, it is assumed that the MN stores the "UP security activation status" including the UP Integrity Protection as a parameter set to "not required", which was applied and used for the DRB established for the first PDU session between the MN and the UE.

[0095] In step 2, the same UE starts a second PDU establishment procedure with the network for redundant data transmission for the second PDU session. The SMF provides the UP security implementation information to the MN when requesting the second PDU session at 904.

[0096] When MN receives a request from the SMF to establish a DRB for a second PDU session between the SN and the UE for redundant data transmission, at 906, instead of transferring the UP security enforcement information received from the SMF, it provides the stored "UP security activation status" to the SN when offloading it to the DRB for the second PDU session used for redundant data transmission. It is not allowed for the SN to modify the UP security activation status received from the MN. This ensures that the same security settings are applied to the DRBs for the first and second PDU sessions established between the UE even if the MN modifies the settings within the UP security enforcement information received from the SMF for the first PDU session.

[0097] Figure 10 shows the signaling flow from TS 23.502 [4] for PDU session establishment.

[0098] Steps 1 to 3 are as described in TS 23.502 [4].

[0099] Step 4: The SMF determines whether the PDU session requires redundancy, and the SMF determines the redundancy sequence number (RSN) as described in 3GPP TS 23.501 [1]. If the SMF determines that redundant handling is not allowed or not possible for a given PDU session, the SMF may reject the establishment of the PDU session based on local policy.

[0100] Steps 5 to 10 are as described in TS 23.502 [4].

[0101] Step 11: From SMF to AMF: Namf_Communication_N1N2MessageTransfer (PDU Session ID, N2 SM information (PDU Session ID, QFI(s), QoS Profile(s), CN Tunnel Info, S-NSSAI from the Allowed NSSAI, Session-AMBR, PDU Session Type, User Plane Security Enforcement information, UE Integrity Protection Maximum Data Rate, RSN), N1 SM container (PDU Session Establishment Accept (QoS Rule(s) and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), selected SSC mode, S-NSSAI(s), DNN, allocated IPv4 address, interface identifier, Session-AMBR, selected PDU Session Type, Reflective QoS Timer (if available), P-CSCF address(es), [Always-on PDU Session]))). If multiple UPFs are used for a PDU session, CN Tunnel Info includes the tunnel information related to the UPF terminating N3.

[0102] If applicable, the RSN indicates the RAN node regardless of whether the user plane of a given PDU session will pass through the master RAN or the secondary RAN for the redundant user plane path using dual connectivity.

[0103] Step 12: From AMF to (R)AN: N2 PDU Session Request (N2 SM information, NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept))).

[0104] Referring to FIG. 11A, a method in a core network of a wireless communication system includes receiving a first request (1102) to establish a first protocol data unit (PDU) session between a user equipment (UE) and a user plane function in the core network, generating user plane (UP) security implementation information (1104) to be applied to the first PDU session, and transmitting the UP security implementation information to a RAN node (1106) to establish the first PDU session. The RAN node may be a master node connected to the UE via a data radio bearer. The RAN node may be a gNB or an ng-eNB.

[0105] The method further includes storing the UP security implementation information (1108), receiving a second request (1110) from the user equipment (UE) to establish a second protocol data unit (PDU) session between the user plane function in the core network, and in response to receiving the second request to establish the second PDU session, transmitting the UP security implementation information to the master node serving the UE (1112) to establish the second PDU session using the UP security implementation information.

[0106] The UP security implementation information may be stored by a session management function (SMF) in the core network. In some embodiments, the UP security implementation information may be stored by a policy control function (PCF) or a unified data management (UDM) function in the core network.

[0107] The above method may further include selecting a user plane function for terminating a second PDU session.

[0108] The second PDU session may be established for redundant data transmission with the first PDU session.

[0109] The second PDU session may be carried on a data radio bearer (DRB) established between the UE and a secondary node. The secondary node may be a gNB or an ng-eNB.

[0110] Referring to FIG. 11B, a method in a radio access network (RAN) node of a wireless communication system includes receiving a first request for establishing a first protocol data unit (PDU) session between a user equipment (UE) connected to the RAN node and a user plane function in a core network (1122), and receiving UP security implementation information to be applied to the first PDU session from a core network node (1124). The RAN node establishes the first PDU session using the UP security implementation information (1126). The above method further includes receiving a second request for establishing a second protocol data unit (PDU) session between the UE and the user plane function in the core network (1128), receiving UP security implementation information from the core network node (1130), and establishing the second PDU session using the UP security implementation information (1132).

[0111] The RAN node may be a master node, and the above method may further include establishing a dual connectivity (DC) connection between the UE and a secondary node, and allocating the second PDU session to the DC connection.

[0112] The method may further include transmitting UP security enforcement information received from a core network node for application to a second PDU session to a secondary node.

[0113] Referring to FIG. 12, a method at a radio access network (RAN) node of a wireless communication system includes receiving a first request to establish a first protocol data unit (PDU) session between a user equipment (UE) connected to the RAN node and a user plane function in a core network (1202), and receiving user plane (UP) security enforcement information from the core network node to be applied to the first PDU session (1204).

[0114] The RAN node modifies the UP security enforcement information to provide modified UP security enforcement information (1206), and uses the modified UP security enforcement information to establish the first PDU session (1208). The method further includes receiving a second request to establish a second protocol data unit (PDU) session between the UE and a user plane function in the core network (1210), receiving UP security enforcement information from the core network node (1212), and using the modified UP security enforcement information to establish the second PDU session (1214).

[0115] The method may further include storing the modified UP security enforcement information.

[0116] The RAN node may be a master node, and the method may further include establishing a dual connectivity (DC) connection between the UE and a secondary node, and allocating the second PDU session to the DC connection.

[0117] The method may further include transmitting the modified UP security enforcement information to the secondary node for application to the second PDU session.

[0118] The second PDU session may be carried on a data radio bearer (DRB) established between the UE and the secondary node.

[0119] The core network node may be responsible for a session management function (SMF).

[0120] FIG. 13 is a block diagram of a Radio Access Network (RAN) node 200 according to some embodiments configured to perform the operations depicted in FIGS. 11B and 12.

[0121] In particular, FIG. 13 illustrates a method for making a Cellular 2 illustrates an example of a Radio Access Network (RAN) node 200 (also referred to as a base station, eNB, eNodeB, gNB, gNodeB, etc.) of a wireless communication network configured to provide communications. The network node 200 may correspond to a central unit, a radio unit, or a combination of a central unit and a radio unit in a RAN node. As shown, the network node 200 may include a transceiver circuit 202 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink wireless communications with wireless devices. The network node 200 may include a network interface circuit 204 (also referred to as a network interface) configured to provide communications with other nodes of the wireless communication network (e.g., with other base stations and / or core network nodes). The network node 200 may also include a processing circuit 206 (also referred to as a processor) coupled to the transceiver circuit 202, and a memory circuit 208 (also referred to as a memory) coupled to the processing circuit 206. The memory circuitry 208 may include computer readable program code that, when executed by the processing circuitry 206, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuitry 206 may be defined as including memory, such that a separate memory circuitry is not required.

[0122] As discussed herein, the operation of network node 200 may be performed by processor 206, network interface 204, and / or transceiver 202. For example, processor 206 may control transceiver 202 to transmit downlink communications to one or more UEs over a radio interface through transceiver 202, and / or to receive uplink communications from one or more UEs over a radio interface through transceiver 202. Similarly, processor 206 may control network interface 204 to transmit communication signals to one or more other network nodes through network interface 204, and / or to receive communication signals from one or more other network nodes through network interface 204. Moreover, a group of modules may be stored in memory 208, and the group of modules may provide instruction groups such that when the instruction groups of a certain module are executed by processor 206, processor 206 performs respective operations (e.g., the operations discussed below with respect to the exemplary embodiments). Additionally, a structure similar to that of FIG. 10 may be used to implement other network nodes, for example, while omitting transceiver 202. Moreover, the network nodes discussed herein may be implemented as virtual network nodes.

[0123] FIG. 14 is a block diagram of a core network node 300 according to some embodiments configured to perform the operations depicted in FIG. 11A.

[0124] In particular, FIG. 14 depicts an example of a core network node 300 of a core network, such as a 5GC or EPC core network. As illustrated, the network node 300 includes a network interface circuit 304 (also referred to as a network interface) configured to provide communication with other nodes of the wireless communication network (e.g., with other base stations and / or core network nodes). The network node 300 may also include a processing circuit 306 (also referred to as a processor), and a memory circuit 308 (also referred to as a memory) coupled to the processing circuit 306. The memory circuit 308 may include computer-readable program code that, when executed by the processing circuit 306, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 306 may be defined as including a memory so as not to require a separate memory circuit.

[0125] As discussed herein, the operations of the network node 300 may be performed by the processor 306 and / or the network interface 304. For example, the processor 306 may control the network interface 304 to transmit communication signals through the network interface 304 to one or more other network nodes and / or receive communication signals through the network interface from one or more other network nodes. Moreover, a group of modules may be stored in the memory 308, and the group of modules may provide instruction groups such that when an instruction group of a certain module is executed by the processor 306, the processor 306 performs respective operations (e.g., the operations discussed herein with respect to the exemplary embodiments). In addition, a structure similar to that of FIG. 14 may be used to implement other network nodes. Moreover, the network nodes discussed herein may be implemented as virtual network nodes.

[0126] Accordingly, a core network node 300 according to some embodiments includes a processing circuit 306 and a memory 308 coupled to the processing circuit, the memory including machine-readable program instructions that, when executed by the processing circuit, cause the network node to perform the operations described herein.

[0127] List of Exemplary Embodiments

[0128] Exemplary embodiments are discussed below. Reference numbers / codes are provided in parentheses in an exemplary / summary form without limiting the exemplary embodiments to specific elements indicated by the reference numbers / codes.

[0129] Embodiment 1: A method performed by a core network node in a core network of a wireless communication system, the method comprising: receiving (1102) a first request from a user equipment (UE) to establish a first protocol data unit (PDU) session with a user plane function within the core network; generating (1104) user plane (UP) security implementation information to be applied to the first PDU session; transmitting (1106) the UP security implementation information to a master node serving the UE to establish the first PDU session; and storing (1108) the UP security implementation information for use in establishing subsequent PDU sessions for the UE.

[0130] Embodiment 2: The method according to Embodiment 1, further comprising: receiving (1110) a second request from a user equipment (UE) to establish a second PDU session with the user plane function within the core network.

[0131] Embodiment 3: The method according to Embodiment 2, further comprising: A method comprising transmitting the UP security implementation information to a master node serving the UE to establish the second PDU session (1112).

[0132] Embodiment 4: The method according to any one of Embodiments 1 to 3, wherein storing the UP security implementation information is performed by a session management function (SMF) in the core network.

[0133] Embodiment 5: The method according to any one of Claims 1 to 4, further comprising selecting a user plane function for terminating the second PDU session.

[0134] Embodiment 7: The method according to any one of Embodiments 1 to 6, wherein the second PDU session is established for redundant data transmission with the first PDU session.

[0135] Embodiment 8: The method according to any one of Embodiments 1 to 7, wherein the second PDU session is carried on a data radio bearer (DRB) established between the UE and a secondary node.

[0136] Embodiment 9: The method according to any one of Embodiments 1 to 8, wherein storing the UP security implementation information is performed by the core network.

[0137] Embodiment 10: The method according to Embodiment 9, wherein storing the UP security implementation information is performed by a policy control function (PCF) or a unified data management (UDM) function in the core network.

[0138] Embodiment 11: A core network node (300), a processing circuit (306), a network interface (304) connected to the processing circuit, A memory (308) connected to the processing circuit, wherein the memory includes machine-readable program instructions that, when executed by the processing circuit, cause the network node to perform operations including the operations described in any one of Embodiments 1 to 10, the core network node.

[0139] Embodiment 12: A computer program including program code executed by a processing circuit (306) of a core network (CN) node (300) configured to operate in a communication network, wherein execution of the program code causes the CN node (300) to perform the operations described in any one of Embodiments 1 to 10, the computer program.

[0140] Embodiment 13: A computer program product comprising a non-transitory storage medium including program code executed by a processing circuit (306) of a core network (CN) node (300) configured to operate in a communication network, wherein execution of the program code causes the CN node (300) to perform the operations described in any one of Embodiments 1 to 10, the computer program product.

[0141] Embodiment 14: A method executed by a radio access network node of a wireless communication system, Receiving (1122) a first request for establishing a first protocol data unit (PDU) session between a user equipment (UE) served by the radio access network node and a user plane function in the core network; Receiving (1124) user plane (UP) security implementation information to be applied to the first PDU session from a core network node; Establishing (1126) the first PDU session using the UP security implementation information; Receiving a second request to establish a second protocol data unit (PDU) session between the UE and the user plane function within the core network (1128); Receiving the UP security implementation information from the core network node (1130); Establishing the second PDU session using the UP security implementation information (1132), a method.

[0142] Embodiment 15: The method according to Embodiment 14, further comprising: Establishing a dual connectivity (DC) connection between the UE and a secondary node; Allocating the second PDU session to the DC connection, a method.

[0143] Embodiment 17: The method according to Embodiment 15, further comprising: Transmitting the UP security implementation information received from the core network node for application to the second PDU session to the secondary node.

[0144] Embodiment 17: The method according to any one of Embodiments 14 to 16, wherein the second PDU session is carried on a data radio bearer (DRB) established between the UE and a secondary node.

[0145] Embodiment 18: The method according to any one of Embodiments 14 to 17, wherein the core network node is in charge of a session management function (SMF).

[0146] Embodiment 19: A method performed by a radio access network node of a wireless communication system, comprising: Receiving a first request to establish a first protocol data unit (PDU) session between a user equipment (UE) served by the wireless access network node and a user plane function in the core network (1202); Receiving user plane (UP) security implementation information from a core network node to be applied to the first PDU session (1204); Modifying the UP security implementation information to provide modified UP security implementation information (1206); Storing the modified UP security implementation information for use in setting up subsequent PDU sessions for the UE (1206); Establishing the first PDU session using the modified UP security implementation information (1208), a method comprising.

[0147] Embodiment 20: The method according to embodiment 19, further comprising Receiving a second request to establish a second protocol data unit (PDU) session between the UE and the user plane function in the core network (1210); Receiving the UP security implementation information from the core network node (1212); Establishing the second PDU session using the modified UP security implementation information (1214), a method comprising.

[0148] Embodiment 21: The method according to embodiment 19 or 20, further comprising Establishing a dual connectivity (DC) connection between the UE and a secondary node; Allocating the second PDU session to the DC connection, a method comprising.

[0149] Embodiment 22: The method according to embodiment 21, further comprising A method comprising transmitting the modified UP security enforcement information to the secondary node for application to the second PDU session.

[0150] Embodiment 23: The method according to any one of Embodiments 19 to 22, wherein the second PDU session is carried on a data radio bearer (DRB) established between the UE and the secondary node.

[0151] Embodiment 24: The method according to any one of Embodiments 19 to 23, wherein the core network node is in charge of a session management function (SMF).

[0152] Embodiment 25: A radio access network (RAN) node (200) comprising a processing circuit (206), a network interface (204) connected to the processing circuit, and a memory connected to the processing circuit, the memory including machine-readable program instructions that, when executed by the processing circuit, cause the RAN node to perform operations including the operations according to any one of Embodiments 14 to 24.

[0153] Embodiment 19: A computer program including program code executed by a processing circuit (206) of a radio access network (RAN) node (200) configured to operate in a communication network, wherein execution of the program code causes the RAN node (200) to perform the operations according to any one of Embodiments 14 to 24.

[0154] A computer program product comprising a non - transitory storage medium including program code executed by a processing circuit of a radio access network (RAN) node (200) configured to operate in a communication network, wherein execution of the program code causes the RAN node (200) to perform the operations according to any one of Embodiments 14 - 24.

[0155] Explanations of the abbreviations in the above disclosure are provided below. <Abbreviation> <Explanation> 3GPP Third Generation Partnership Project 5G Fifth Generation AAA Authentication, Authorization, and Accounting ABBA Architecture - to - Architecture Anti - Videoding Down AF Application Function AKA Authentication and Key Agreement AMF Access and Mobility Management Function AN Access Network AUSF Authentication Server Function ARPF Authentication Credential Repository and Processing Function AS Access Stratum AV Authentication Vector BBF Broadband Forum CA Certification Authority CN Core Network RNTI Radio Network Temporary Identifier DN Data Network EAP Extensible Authentication Protocol EMSK Extended Master Session Key eNB Evolved Node B (radio base station in LTE) FAGF Fixed Access Gateway Function FN - RG Fixed Network Residential Gateway gNB Radio base station in NR HPLMN Home PLMN HN Home Network IETF Internet Engineering Task Force KDF Key Derivation Function LTE Long Term Evolution MSB Most Significant Bit MSK Master Session Key ME Mobile Equipment MNC Mobile Network Core MCC Mobile Country Code NAS Non-Access Stratum NF Network Function NRF NF Repository Function NEF Network Exposure Function NSSF Network Slice Selection Function NPN Non-Public Network NR New Radio OCSP Online Certificate Status Protocol PCF Policy Control Function PLMN Public Land Mobile Network RAN Radio Access Network RFC Request for Comments SBA Service-Based Architecture SLA Service Level Agreement SMF Session Management Function SEAF Security Anchor Function SUPI Subscriber Permanent Identifier SUCI Subscriber Concealed Identifier TLS Transport Layer Security USIM Universal Subscriber Identity Module UDM Unified Data Management UPF User Plane Function UE User Equipment VPLMN Visited PLMN W-5GAN Wireline 5G Access Node X2 Interface / Reference Point between Two eNBs Xn Interface / Reference Point between Two gNBs

[0156] References: [1] 3GPP TS23.501 v15.4.0 [2] 3GPP TR23.725 v16.0.0 [3] 3GPP TS33.401 v15.6.0 [4] 3GPP TS23.502 v15.4.1 [5] 3GPP TS37.340 v15.4.0 [6] 3GPP TS33.501 v15.3.1

[0157] Further definitions and embodiments are discussed below.

[0158] In the above description of various embodiments of the inventive concept, it should be understood that the technical terms used therein are for the purpose of merely describing specific embodiments and are not intended to limit the inventive concept. Unless otherwise defined, all terms (including technical and academic terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the inventive concept pertains. Further, it will be understood that the terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art, such as in a commonly used dictionary, and should not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0159] When an element is referred to as being "connected", "coupled", "responsive", or a derivative thereof to another element, it may be directly connected to, coupled to, or responsive to the other element, and intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or a derivative thereof to another element, intervening elements are not present. Throughout, like numbers refer to like elements. Further, as used herein, "coupled", "connected", "responsive", or a derivative thereof may include wireless coupling, connection, or response. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or structures may not be described in detail for the sake of brevity and / or clarity. The term "and / or" includes any and all combinations of one or more of the associated listed items.

[0160] Although the terms first, second, third, etc. may be used herein to describe various elements / acts, it will be understood that these elements / acts are not to be limited by these terms. These terms are only used to distinguish one element / act from another. Thus, a first element / act in some embodiments may be referred to as a second element / act in other embodiments without departing from the teachings of the inventive concept. The same reference numbers or the same reference designators represent the same or similar elements throughout this specification.

[0161] As used herein, the terms "comprise," "comprising," "include," "including," "have," "has," "having," or derivatives thereof are open-ended and include one or more of the recited features, integers, elements, steps, components, or functions without excluding the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Further, as used herein, the common abbreviation "e.g." (for example), which is derived from the Latin phrase "exempli gratia," is used to introduce or identify one or more general examples of the item(s) previously mentioned and is not intended to limit such item(s). The common abbreviation "i.e." (that is), which is derived from the Latin phrase "id est," may be used to identify specific items from a more general description.

[0162] Exemplary embodiments are described herein with reference to block diagrams and / or flowcharts of methods, apparatus (systems and / or devices), and / or computer program products implemented by computers. It will be understood that one block in the block diagram and / or flowchart description, as well as combinations of multiple blocks in the block diagram and / or flowchart description, can be implemented by a set of computer program instructions executed by one or more computer circuits. These sets of computer program instructions may be provided to the processor circuits of general-purpose computer circuits, special-purpose computer circuits, and / or other programmable data processing circuits for producing machines, whereby the instructions executed via the processors of the computer and / or other programmable data processing devices transform and control transistors, values stored in memory locations, and other hardware components within such circuits to implement the functions / operations specified in one or more blocks of the block diagram and / or flowchart, thereby generating means (functionality) and / or structures for implementing the functions / operations specified in the blocks of the block diagram and / or flowchart.

[0163] These sets of computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing device to function in a particular manner, whereby the product produced by the instructions stored in the computer-readable medium includes instructions for implementing the functions / operations specified in one or more blocks of the block diagram and / or flowchart. Accordingly, embodiments of the inventive concept may be embodied in hardware and / or software operating on a processor such as a digital signal processor (including firmware, resident software, microcode, etc.), which may be generically referred to by the terms "circuit," "module," or derivatives thereof.

[0164] It should also be noted that in some alternative implementations, the functions / operations described within a block may occur in an order different from the order described in the flowchart. For example, two blocks shown consecutively may actually be executed substantially in parallel, or they may be executed in the reverse order depending on the functionality / operation involved. Moreover, the functionality of a given block in a flowchart and / or block diagram may be divided into multiple blocks, and / or the functionality of two or more blocks in a flowchart and / or block diagram may be at least partially integrated. Finally, without departing from the scope of the inventive concept, other blocks may be added / inserted between the illustrated blocks, and blocks / operations may be omitted. Moreover, although some of the figures include arrows on communication paths to indicate the main direction of communication, it should be understood that communication may occur in the opposite direction to the drawn arrows.

[0165] Without substantially departing from the principles of the inventive concept, many variations and modifications can be made to the above embodiments. All such variations and modifications are hereby intended to be included within the scope of the inventive concept. Accordingly, the summary disclosed above is for illustrative purposes only and should not be regarded as limiting, and the examples of embodiments are intended to cover all such modifications, extensions, and other embodiments that fall within the spirit and scope of the inventive concept. Thus, to the maximum extent permitted by law, the scope of the inventive concept should be determined by the broadest permissible interpretation of this disclosure, including the examples of those embodiments and their equivalents, and should not be limited or restricted by the detailed description thus far.

[0166] Additional explanations are provided below.

[0167] Generally, all terms used herein should be interpreted according to their ordinary meanings in the relevant technical field, unless a different meaning is clearly given and / or suggested by the context in which they are used. All references to an element, apparatus, component, means, step, etc. should be construed openly as a reference to at least one instance of those elements, apparatus, components, means, steps, etc., unless otherwise explicitly stated. Any method step disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or it is implicitly understood that a step must follow or precede another step. Any feature of any embodiment disclosed herein may be applied to any other embodiment, if appropriate. Similarly, any advantage of any embodiment may apply to any other embodiment, and vice versa. Other objects, features, and advantages of the embodiments included will become apparent from the following description.

[0168] Some of the embodiments contemplated herein will be described more fully hereinafter with reference to the accompanying drawings. However, other embodiments are also included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to only the embodiments illustrated herein. Rather, those embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0169] Figure 15: Wireless Network According to Some Embodiments

[0170] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein will be described in the context of a wireless network, such as the exemplary wireless network shown in FIG. 15. For simplicity, only network QQ106, network nodes QQ160 and QQ160b, and WD QQ110, QQ110b, and QQ110c are depicted in the wireless network of FIG. 15. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and other communication devices, such as landline telephones, service providers, or some other network node or end device. Of the components shown, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network. (also referred to as a mobile terminal) Only are depicted. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and other communication devices, such as landline telephones, service providers, or some other network node or end device. Of the components shown, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0171] The wireless network may include any type of communication, telecommunications, data, cellular, and / or wireless network or other similar type of system, and / or interface therewith. In some embodiments, the wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of the wireless network may implement communication standards such as GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), LTE (Long Term Evolution) and / or other suitable 2G, 3G, 4G or 5G standards, WLAN (Wireless Local Area Network) standards such as IEEE802.11 standards, and / or any other suitable wireless communication standards such as WiMax (Worldwide Interoperability for Microwave Access), Bluetooth, Z-Wave and / or ZigBee standards.

[0172] Network QQ106 may include one or more backhaul networks, core networks, IP networks, PSTN (Public Switched Telephone Networks), packet data networks, optical networks, WAN (Wide-Area Networks), LAN (Local Area Networks), WLAN (Wireless Local Area Networks), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0173] Network nodes QQ160 and WD QQ110 include various components that are described in more detail below. These components work in cooperation to provide functionality of network nodes and / or wireless devices, such as providing a wireless connection in a wireless network. In various embodiments, a wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relays, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether wired or wireless.

[0174] As used herein, a network node is a device that can communicate directly or indirectly with wireless devices and / or other network nodes, and is configured, arranged, and / or operable as such, or enables and / or provides wireless access to wireless devices, and / or performs other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points) and base stations (BSs) (e.g., wireless base stations, Node B, evolved Node B (eNB), and NR Node B (gNB)). Base stations may be categorized based on the amount of coverage they provide (or equivalently, their transmission power levels), in which case they may also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may also be a relay donor node that controls relay nodes or relays. A network node may include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), which may also be referred to as a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna, such as an antenna-integrated radio. A part of a distributed radio base station may also be referred to as a node within a distributed antenna system (DAS). Another example of a network node is a multi-standard radio (MSR) device such as an MSR BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node as described in more detail below.However, more generally, a network node can enable and / or provide access to a wireless network to a wireless device, or provide some service to a wireless device accessing the wireless network, and can represent any suitable device (or collection of devices) so configured, arranged, and / or operable.

[0175] In FIG. 15, network node QQ160 includes a processing circuit QQ170, a device-readable medium QQ180, an interface QQ190, auxiliary equipment QQ184, a power supply QQ186, a power circuit QQ187, and an antenna QQ162. Although the network node QQ160 shown in the exemplary wireless network of FIG. 15 can represent a device including the illustrated combination of hardware components, other embodiments may include network nodes with different combinations of components. It should be understood that a network node can include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Moreover, the components of network node QQ160 are depicted as a single box located within a larger box or nested within multiple boxes, but in reality, a network node can include multiple different physical components that make up the single illustrated component (e.g., device-readable medium QQ180 can include multiple RAM modules along with multiple separate hard drives).

[0176] Similarly, network node QQ160 may be composed of a plurality of physically distinct components (e.g., node B components and RNC components, or BTS components and BSC components, etc.) that each of its respective components may have. In a scenario where network node QQ160 comprises a plurality of distinct components (e.g., BTS and BSC components), one or more of those distinct components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such scenarios, each unique pair of node B and RNC may, in some instances, be regarded as a single distinct network node. In some embodiments, network node QQ160 may be configured to support a plurality of radio access technologies (RATs). In such embodiments, some components may be made redundant (e.g., distinct device-readable media QQ180 for different RATs), and some components may be reused (e.g., the same antenna QQ162 may be shared by those RATs). Network node QQ160 may include a plurality of sets of various exemplary components for various wireless technologies, such as wireless technologies integrated into network node QQ160, like GSM, WCDMA, LTE, NR, WiFi, or Bluetooth. Those wireless technologies may be integrated into the same or different chips or sets of chips and other components within network node QQ160.

[0177] The processing circuit QQ170 is configured to perform some determination, calculation, or similar operation (such as a certain acquisition operation) described herein as provided by a network node. These operations performed by the processing circuit QQ170 may include, for example, converting the acquired information into other information, comparing the acquired information or the converted information with the information stored in the network node, and / or performing one or more operations based on the acquired information or the converted information, and making a decision as a result of the processing, thereby processing the information acquired by the processing circuit QQ170.

[0178] The processing circuit QQ170 may include one or more combinations of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic, operable to provide the functionality of the network node QQ160 alone or in cooperation with other components of the network node QQ160 such as a device-readable medium QQ180. For example, the processing circuit QQ170 may execute instructions stored in the device-readable medium QQ180 or in a memory within the processing circuit QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit QQ170 may include a system on chip (SOC).

[0179] In some embodiments, the processing circuit QQ170 may include one or more of a radio frequency (RF) transceiver circuit QQ172 and a baseband processing circuit QQ174. In some embodiments, the radio frequency (RF) transceiver circuit QQ172 and the baseband processing circuit QQ174 may be on separate chips (or sets of chips), substrates, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit QQ172 and the baseband processing circuit QQ174 may be on the same chip or set of chips, substrate, or unit.

[0180] In an embodiment, some or all of the functionality described herein as provided by a network node, base station, eNB, or other such network device may be performed by the processing circuit QQ170 executing instructions stored in a device-readable medium QQ180 or memory within the processing circuit QQ170. In alternative embodiments, some or all of the functionality may be provided by the processing circuit QQ170 in a hardwired manner, such as without executing instructions stored in a separate or discrete device-readable medium. In any of those embodiments, the processing circuit QQ170 can be configured to perform the described functionality, whether or not instructions stored in a device-readable storage medium are executed. The benefits provided by such functionality are enjoyed by the network node QQ160 as a whole, and / or by end users and the wireless network generally, not limited to just the processing circuit QQ170 or other components of the network node QQ160.

[0181] The device-readable medium QQ180 may include any form of volatile or non-volatile computer-readable memory, including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD) or digital video disc (DVD)), and / or any other suitable volatile or non-volatile device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit QQ170. The device-readable medium QQ180 may store any suitable instructions, data, or information, including one or more of computer programs, software, logic, rules, code, tables, etc., that are executable by the processing circuit QQ170 and available for use by the network node QQ160, and / or other instructions. The device-readable medium QQ180 may be used to store any calculation results generated by the processing circuit QQ170 and / or any data received via the interface QQ190. In some embodiments, the processing circuit QQ170 and the device-readable medium QQ180 may be considered integrated.

[0182] Interface QQ190 is used in wired or wireless communication of signaling and / or data among network node QQ160, network QQ106, and / or WDQQ110. As shown in the figure, interface QQ190 includes, for example, port / terminal QQ194 for transmitting and receiving data with network QQ106 over a wired connection. Interface QQ190 also includes a radio front-end circuit QQ192 that can be connected to antenna QQ162 or in some embodiments is part of antenna QQ162. The radio front-end circuit QQ192 includes a filter QQ198 and an amplifier QQ196. The radio front-end circuit QQ192 can be connected to antenna QQ162 and processing circuit QQ170. The radio front-end circuit may be configured to condition signals communicated between antenna QQ162 and processing circuit QQ170. The radio front-end circuit QQ192 can receive digital data to be transmitted to other network nodes or WDs via a wireless connection. The radio front-end circuit QQ192 can convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filter QQ198 and / or amplifier QQ196. The radio signal can then be transmitted via antenna QQ162. Similarly, when data is received, antenna QQ162 collects the radio signal, and then the radio signal can be converted into digital data by radio front-end circuit QQ192. The digital data can be passed to processing circuit QQ170. In other embodiments, the interface may include different components and / or different combinations of components.

[0183] In an alternative embodiment, the network node QQ160 may not include a separate radio front-end circuit QQ192. Instead, the processing circuit QQ170 may include a radio front-end circuit and may be connected to the antenna QQ162 without a separate radio front-end circuit QQ192. Similarly, in some embodiments, all or some of the RF transceiver circuits QQ172 may be considered part of the interface QQ190. In yet another embodiment, the interface QQ190 may include one or more ports or terminals QQ194, a radio front-end circuit QQ192, and an RF transceiver circuit QQ172 as part of a wireless unit (not shown), and the interface QQ190 may communicate with a baseband processing circuit QQ174 that is part of a digital unit (not shown).

[0184] The antenna QQ162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. The antenna QQ162 may be coupled to the radio front-end circuit QQ190 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna QQ162 may include one or more omnidirectional antennas, sector antennas, or panel antennas operable to transmit and receive wireless signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas may be used to transmit and receive wireless signals in any direction, sector antennas may be used to transmit and receive wireless signals from devices within a specific area, and panel antennas may be line-of-sight antennas used to transmit and receive relatively linear wireless signals. In some examples, the use of more than one antenna may be referred to as MIMO. In one embodiment, the antenna QQ162 may be separate from the network node QQ160 and may be connectable to the network node QQ160 through an interface or port.

[0185] Antenna QQ162, interface QQ190, and / or processing circuit QQ170 may be configured to perform any of the receiving operations and / or any of the acquisition operations described herein as being performed by a network node. Any information, data, and / or signal may be received from a wireless device, other network node, and / or any other network equipment. Similarly, antenna QQ162, interface QQ190, and / or processing circuit QQ170 may be configured to perform any of the transmitting operations described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a wireless device, other network node, and / or any other network equipment.

[0186] Power circuit QQ187 may include a power management circuit or be coupled to a power management circuit and is configured to supply power to the components of network node QQ160 for performing the functionality described herein. Power circuit QQ187 may receive power from power source QQ186. Power source QQ186 and / or power circuit QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for each component (e.g., at the voltage and current levels required for each respective component). Power source QQ186 may be either included in power circuit QQ187 and / or network node QQ160 or external thereto. For example, network node QQ160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to power circuit QQ187. As a further example, power source QQ186 may include a source of power in the form of a battery or battery pack connected to or integrated with power circuit QQ187. The battery may provide backup power in case of a failure of an external power source. Other types of power sources such as a solar power generation device may also be used.

[0187] Alternative embodiments of network node QQ160 may include additional components other than those shown in FIG. 15 that may be responsible for providing a functional perspective of the network node that includes any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include a user interface device that enables input of information to network node QQ160 and enables output of information from network node QQ160. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions on network node QQ160.

[0188] As used herein, a wireless device (WD) is a device that is capable of wirelessly communicating with a network node and / or another wireless device, and is so configured, arranged, and / or operable. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may include transmitting and / or receiving a wireless signal using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information through the air. In some embodiments, the WD may be configured to transmit and / or receive information without direct human interaction. For example, the WD may be designed to transmit information to the network at a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, VoIP (Voice over IP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer premise equipment (CPE), vehicle-mounted wireless terminal devices, etc. The WD may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2E), and may be referred to as a D2D communication device in this case. As another specific example, in the scenario of the Internet of Things (IoT), the WD may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to other WDs and / or network nodes.In this case, the WD may be a machine-to-machine (M2M) device and may be referred to as an MTC device in the context of 3GPP. As one specific example, the WD may be a 3GPP narrowband. Internet of Things It may be a UE implementing the (NB-IoT) standard. Specific examples of such machines or devices are sensors, meter devices such as power meters, industrial machines, household or personal electrical appliances (e.g., refrigerators, TVs, etc.), or personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other device capable of monitoring and / or reporting on its operating status or other functions associated with its operation. The WD as described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Further, the WD as described above may be mobile, in which case it may be referred to as a mobile device or mobile terminal.

[0189] As shown, the wireless device QQ110 includes an antenna QQ111, an interface QQ114, a processing circuit QQ120, a device-readable medium QQ130, a user interface device QQ132, an auxiliary device QQ134, a power supply QQ136, and a power circuit QQ137. The WD QQ110 may include one or more sets of the illustrated components for various wireless technologies supported by the WD QQ110, such as, by way of example only, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies. Those wireless technologies may be integrated into the same or different chips within the WD QQ110 or a set of chips as other components.

[0190] Antenna QQ111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface QQ114. In some alternative embodiments, antenna QQ111 may be separate from WDQQ110 and may be connectable to WDQQ110 through an interface or port. Antenna QQ111, interface QQ114, and / or processing circuit QQ120 may be configured to perform any of the receiving or transmitting operations described herein as being performed by the WD. Any information, data, and / or signals may be received from network nodes and / or other WDs. In some embodiments, the radio front-end circuit and / or antenna QQ111 may be regarded as an interface.

[0191] As shown, interface QQ114 includes a wireless front - end circuit QQ112 and an antenna QQ111. The wireless front - end circuit QQ112 includes one or more filters QQ118 and an amplifier QQ116. The wireless front - end circuit QQ114 is connected to the antenna QQ111 and the processing circuit QQ120 and is configured to condition the signals communicated between the antenna QQ111 and the processing circuit QQ120. The wireless front - end circuit QQ112 may be coupled to the antenna QQ111 or may be part of the antenna QQ111. In some embodiments, WDQQ110 may not include a separate wireless front - end circuit QQ112; rather, the processing circuit QQ120 may include a wireless front - end circuit and may be connected to the antenna QQ111. Similarly, in some embodiments, some or all of the RF transceiver circuit QQ122 may be considered part of the interface QQ114. The wireless front - end circuit QQ112 may receive digital data to be transmitted to other network nodes or WDs via a wireless connection. The wireless front - end circuit QQ112 may convert the digital data into a wireless signal having appropriate channel and bandwidth parameters using a combination of the filter QQ118 and / or the amplifier QQ116. And the wireless signal may be transmitted via the antenna QQ111. Similarly, when data is received, the antenna QQ111 collects the wireless signal, and then the wireless signal may be converted into digital data by the wireless front - end circuit QQ112. The digital data may be passed to the processing circuit QQ120. In other embodiments, the interface may include different components and / or different combinations of components.

[0192] The processing circuit QQ120 may include one or more combinations of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other suitable computing device, resource, or hardware, software, and / or encoded logic, operable to provide the functionality of the WD QQ110, either alone or in cooperation with other components of the WD QQ110 such as a device-readable medium QQ130. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit QQ120 may execute instructions stored in a device-readable medium QQ130 or in a memory within the processing circuit QQ120 to provide the functionality disclosed herein.

[0193] As illustrated, the processing circuit QQ120 includes one or more of the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In one embodiment, the processing circuit QQ120 of the WD QQ110 may include a system-on-a-chip (SOC). In some embodiments, the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126 may be on separate chips or a set of chips. In an alternative embodiment, some or all of the baseband processing circuit QQ124 and the application processing circuit QQ126 may be combined onto one chip or a set of chips, and the RF transceiver circuit QQ122 may be on a separate chip or a set of chips. In a further alternative embodiment, some or all of the RF transceiver circuit QQ122 and the baseband processing circuit QQ124 may be on the same chip or a set of chips, and the application processing circuit QQ126 may be on a separate chip or a set of chips. In yet another alternative embodiment, some or all of the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126 may be combined on the same chip or a set of chips. In some embodiments, the RF transceiver circuit QQ122 may be part of the interface QQ114. The RF transceiver circuit QQ122 may condition RF signals for the processing circuit QQ120.

[0194] In one embodiment, some or all of the functionality described herein as being performed by the WD may be provided by executing instructions stored on a device-readable medium QQ130, which may be a computer-readable storage medium in some embodiments, by a processing circuit QQ120. In an alternative embodiment, some or all of that functionality may be provided by the processing circuit QQ120 in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of those specific embodiments, the processing circuit QQ120 may be configured to perform the functionality described, whether or not instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are enjoyed by the WD QQ110 as a whole, and / or by the end user and the wireless network in general, without being limited to the processing circuit QQ120 alone or other components of the WD QQ110.

[0195] The processing circuit QQ120 may be configured to perform any of the decisions, calculations, or similar operations (e.g., an acquisition operation) described herein as being performed by the WD. Such operations as performed by the processing circuit QQ120 may include processing information obtained by the processing circuit QQ120, for example, by converting the obtained information to other information, comparing the obtained information or the converted information with information stored in the WD QQ110, and / or performing one or more operations based on the obtained information or the converted information, and making a decision as a result of that processing. 。

[0196] The device-readable medium QQ130 may be operable to store one or more of a computer program, software, logic, rules, code, tables, etc., executable by the processing circuit QQ120, and / or other instructions. The device-readable medium QQ130 may include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable medium (e.g., a CD (Compact Disk) or a DVD (Digital Video Disk)), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 120. In some embodiments, the processing circuit QQ120 and the device-readable medium QQ130 may be considered integrated. The user interface device QQ132 may provide components that enable a human user to interact with the WD QQ110. Such interactions may take many forms, such as visual, auditory, tactile, etc. The user interface device QQ132 may be operable to generate output to the user and enable the user to provide input to the WD QQ110. The type of interaction may vary depending on the type of user interface device QQ132 attached to the WD QQ110. For example, if the WD QQ110 is a smartphone, the interaction may be via a touch screen; if the WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an alarm sound (e.g., when smoke is detected). The user interface device QQ132 may include an input interface, devices, and circuits, and an output interface, devices, and circuits. The user interface device QQ132 is configured to enable the input of information to the WD QQ110 and is connected to the processing circuit QQ120 to enable the processing circuit QQ120 to process the input information.The user interface device QQ132 may include, for example, a microphone, a proximity or other sensor, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device QQ132 is also configured to enable the output of information from the WD QQ110 and to enable the processing circuitry QQ120 to output information from the WD QQ110. The user interface device QQ132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone interface, or other output circuitry. Using one or more input / output interfaces, devices, and circuitry of the user interface device QQ132, the WD QQ110 may communicate with an end user and / or a wireless network and enable them to benefit from the functionality described herein.

[0197] The auxiliary device QQ134 is operable to provide more specific functionality that may not generally be performed by the WD. It may include, for example, dedicated sensors for making measurements for various purposes, interfaces for additional types of communication such as wired communication, and the like. Whether to include them and the components of the auxiliary device QQ134 may vary depending on the embodiment and / or scenario.

[0198] Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. Power source QQ136 may further include a power circuit QQ137 for transmitting power from power source QQ136 to various parts of WD QQ110 that require power from power source QQ136 to perform any of the functionality described or shown herein. In certain embodiments, power circuit QQ137 may include a power management circuit. Additionally or alternatively, power circuit QQ137 may be operable to receive power from an external power source, in which case WD QQ110 may be connectable to an external power source (such as an electrical outlet) via an input circuit or interface, such as a power cable. In some embodiments, power circuit QQ137 may be operable to transmit power from an external power source to power source QQ136. This may be, for example, for charging power source QQ136. Power circuit QQ137 may perform some shaping, conversion, or other modification to the power from power source QQ136 to make it suitable for each component of WD QQ110 that is a power recipient.

[0199] Figure 16: User Equipment According to Some Embodiments

[0200] FIG. 16 shows one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE need not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user but is not initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user and may be associated with or operated for the benefit of a user. UE QQ 200It may be any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an Extended MTC (eMTC) UE. UE QQ200 as shown in Figure 16 is one example of a WD configured for communication according to one or more communication standards released by 3GPP, such as the GSM, UMTS, LTE, and / or 5G standards of 3GPP. As mentioned previously, the terms WD and UE may be used interchangeably. Therefore, although it is a UE in Figure 16, the components discussed here are equally applicable to WD, and vice versa.

[0201] In Figure 16, UE QQ200 includes a processing circuit 201 operably connected to an input / output interface QQ205, a radio frequency (RF) interface 209, a network connection interface QQ211, a memory QQ215 including a random access memory (RAM) QQ217, a read-only memory (ROM) QQ219, and a storage medium QQ211, a communication subsystem QQ231, a power supply QQ233, and / or any other components, or any combination thereof. The storage medium QQ221 includes an operating system QQ223, an application program QQ225, and data QQ227. In other embodiments, the storage medium QQ221 may include other similar types of information. A UE may utilize all of the components shown in Figure 16, or only a subset of those components. The level of integration between components may vary between one UE and another. Furthermore, a UE may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0202] In FIG. 16, processing circuit QQ201 can be configured to process computer instructions and data. The processing circuit QQ201 can be implemented as any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in memory, such as a hardware-implemented state machine (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more stored programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit QQ201 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0203] In the illustrated embodiment, the input / output interface QQ205 may be configured to provide a communication interface for input devices, output devices, and input / output devices. The UE QQ200 may be configured to use an output device via the input / output interface QQ205. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to and output from the UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, other output devices, or any combination thereof. The UE QQ200 may be configured to use an input device via the input / output interface QQ205 to enable a user to capture information to the UE QQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, and a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor for sensing input from a user. The sensor may be, for example, an accelerometer, a gyroscope, an inclination sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, other similar sensors, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0204] In FIG. 16, the RF interface QQ209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface QQ211 can be configured to provide a communication interface to the network QQ243a. The network QQ243a can include wired and / or wireless networks such as a LAN (Local-Area Network), a WAN (Wide-Area Network), a computer network, a wireless network, a telecommunications network, other similar networks, or any combination thereof. For example, the network QQ243a may include a Wi-Fi network. The network connection interface QQ211 can be configured to include a receiver and a transmitter interface used to communicate with one or more other devices on a communication network according to one or more communication protocols such as Ethernet, TCP / IP, SONET, or ATM. The network connection interface QQ211 can implement receiver and transmitter functionality appropriate for a communication network link (e.g., optical and electrical). The receiver and transmitter functions may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0205] RAM QQ217 can be configured to interface with processing circuit QQ201 via bus QQ202 to provide storage and caching of data or computer instructions during the execution of software programs such as operating systems, application programs, and device drivers. ROM QQ219 can be configured to provide computer instructions or data to processing circuit QQ201. For example, ROM QQ219 can be configured to store invariant low-level system code or data for basic system functions stored in non-volatile memory, such as basic I / O (basic input and output), startup, or reception of keystrokes from a keyboard. Storage medium QQ221 can be configured to include memory such as RAM, ROM, PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, storage medium QQ221 can be configured to include application programs QQ225 such as operating system QQ223, web browser application, widget or gadget engine, or other applications, and data files QQ227. Storage medium QQ221 can store any of a wide variety of operating systems or combinations of multiple operating systems for use by UE QQ200.

[0206] The memory medium QQ221 can be configured to include a plurality of physical drive units such as RAID (Redundant Array of Independent Disks), floppy disk drives, flash memories, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, HD-DVD (High-Density Digital Versatile Disc), optical disk drives, internal hard disk drives, Blu-Ray optical disk drives, HDDS (Holographic Digital Data Storage) optical disk drives, external mini DIMM (Dual In-Line Memory Module), SDRAM (Synchronous Dynamic Random Access Memory), external micro DIMM SDRAM, and smart card memories such as SIM / RUIM (Subscriber Identity Module or Removable User Identity SIM) modules. The memory medium QQ221 can enable the UE QQ200 to access computer-executable instructions or application programs stored in a temporary or non-temporary memory medium to offload or upload data. Items of products such as those using a communication system can be tangibly embodied in the memory medium QQ221 which may include a device-readable medium.

[0207] In FIG. 16, the processing circuit QQ201 may be configured to communicate with the network QQ243b using the communication subsystem QQ231. The network QQ243a and the network QQ243b may be one or more of the same network or different networks. The communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with the network QQ243b. For example, the communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of other wirelessly communicable devices, such as other WDs, UEs, or base stations of a radio access network (RAN), according to one or more communication protocols such as IEEE802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, or WiMax. Each transceiver may include a transmitter QQ233 and / or a receiver QQ235 that implement the functionality of a transmitter or receiver (e.g., frequency allocation, etc.) appropriate for the RAN link, respectively. Further, the transmitter QQ233 and the receiver QQ235 of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0208] In the illustrated embodiment, the communication functions of the communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as the use of GPS (Global Positioning System) for location determination, other similar communication functions, or any combination thereof. For example, the communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network QQ243b may include wired and / or wireless networks such as a LAN (Local-Area Network), WAN (Wide-Area Network), computer network, wireless network, telecommunications network, other similar networks, or any combination thereof. For example, the network QQ243b may include a cellular network, Wi-Fi network, and / or a proximity network. The power supply QQ213 may be configured to provide power to the components of the UE QQ200 in alternating current (AC) or direct current (DC).

[0209] The features, benefits, and / or functions described herein may be implemented in one of the components of UE QQ200 or may be divided across multiple components of UE QQ200. Further, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In other examples, any of such components may be program instructions stored in memory, represented by such program instructions that perform the corresponding functions described herein when executed by processing circuitry QQ201. In other examples, the functionality of any of such components may be divided between processing circuitry QQ201 and communication subsystem QQ231. In other examples, computationally lightweight functions of any of such components may be implemented in software or firmware and computationally heavy functions may be implemented in hardware.

[0210] Figure 17: Virtualization environment according to some embodiments

[0211] FIG. 17 is a schematic block diagram showing a virtualization environment QQ300 in which functions implemented according to some embodiments can be virtualized. In this context, virtualization means that can generate a virtual version of a device or apparatus may include a virtual hardware platform, a storage device, and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtual base station or a virtual radio access node), a device (e.g., a UE, a wireless device, or any other type of communication device), or components thereof, at least a part of the functionality of which is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0212] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented within one or more virtual environments QQ300 hosted by one or more hardware nodes QQ330. Further, in embodiments where the virtual node is not a radio access node or does not require wireless connectivity (e.g., a core network node), the network node may be virtualized as a whole.

[0213] The above functions may be implemented by one or more applications QQ320 (alternatively, may be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The application QQ320 is executed in a virtualization environment QQ300 that provides hardware QQ330 including a processing circuit QQ360 and a memory QQ390. The memory QQ390 includes a set of instructions QQ395 executable by the processing circuit QQ360, whereby the application QQ320 is operable to provide one or more of the features, benefits, and / or functions disclosed herein.

[0214] The virtualized environment QQ300 includes a general-purpose or special-purpose network hardware device QQ330 or a processing circuit QQ360 that includes a set of one or more processors, which may be COTS (Commercial Off-The-Shelf) processors, dedicated application-specific integrated circuit ( ASIC ) , or any other type of processing circuit including digital or analog hardware components or special-purpose processors. Each hardware device may include a memory QQ390-1 that can be a non-persistent memory for temporarily storing software executed by an instruction group QQ395 or a processing circuit QQ360. Each hardware device may include one or more network interface controllers (NICs) QQ370, also known as network interface cards, that include a physical network interface QQ380. Additionally, each hardware device may include a non-transitory and persistent machine-readable storage medium QQ390-2 that stores software QQ395 and / or instructions executable by the processing circuit QQ360. The software QQ395 may include any type of software including software for instantiating one or more virtualization layers (also referred to as hypervisors) QQ350, software for executing virtual machines QQ340, and software that enables the functions, features, and / or benefits described in some of the embodiments described herein.

[0215] The virtual machine QQ340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage and may be executed by a corresponding virtualization layer QQ350 or hypervisor. Various embodiments of instances of virtual appliances QQ320 may be implemented in one or more of the virtual machines QQ340, and the implementation may be made in various ways.

[0216] During operation, processing circuit QQ360 executes software QQ395 to instantiate a hypervisor or virtualization layer QQ350, which may also be referred to as a virtual machine monitor (VMM). The virtualization layer QQ350 presents a virtual operating platform that appears to the virtual machines QQ340 as networking hardware.

[0217] As shown in FIG. 17, the hardware QQ330 may be a stand-alone network node with general or proprietary components. The hardware QQ330 may include an antenna QQ3225 and may implement some functions via virtualization. Alternatively, the hardware QQ330 may be part of a larger cluster of hardware (such as within a data center or customer premise equipment (CPE)) where multiple hardware nodes cooperate and are managed via MANO (Management and Orchestration) QQ3100, and MANO QQ3100 oversees, among other things, the lifecycle management of the application QQ320.

[0218] In some contexts, the virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many types of network equipment into industry-standard high-capacity server hardware, physical switches, and physical storage that can be located within data centers and customer premise equipment.

[0219] In the context of NFV, the virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine. Each of the virtual machines QQ340, and the portion of the hardware QQ330 that executes the virtual machine, form separate virtual network elements (VNEs), whether the hardware is dedicated to the virtual machine and / or shared by the virtual machine with other virtual machines QQ340.

[0220] Also in the context of NFV, a virtual network function (VNF) is responsible for handling a proprietary network function running in one or more virtual machines QQ340 at the top of a hardware networking infrastructure QQ330, corresponding to the application QQ320 in FIG. 17.

[0221] In some embodiments, one or more radio units QQ3200, each including one or more transmitters QQ3220 and one or more receivers QQ3210, may be coupled to one or more antennas QQ3225. The radio unit QQ3200 may communicate directly with the hardware node QQ330 via one or more suitable network interfaces and may be used in combination with virtual components to provide radio capabilities to a virtual node, such as a radio access node or a base station.

[0222] In some embodiments, some signaling can be made to operate with the use of the control system QQ3230, which may alternatively be used for communication between the hardware node QQ330 and the radio unit QQ3200.

[0223] FIG. 18: A telecommunications network connected to a host computer via an intermediate network according to some embodiments

[0224] Referring to FIG. 18, according to one embodiment, a communication system includes a telecommunication network QQ410 such as a 3GPP - type cellular network, and the telecommunication network QQ410 includes an access network QQ411 such as a radio access network and a core network QQ414. The access network QQ411 includes a plurality of base stations QQ412a, QQ412b, QQ412c such as NB, eNB, gNB, or other types of radio access points, each of which defines a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to the core network QQ414 on a wired or wireless connection QQ415. A first UE QQ491 located in the coverage area QQ413c is configured to be wirelessly connected to or paged by the corresponding base station QQ412c. A second UE QQ492 within the coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. In this example, although a plurality of UEs QQ491, QQ492 are illustrated, the disclosed embodiments are equally applicable to situations where there is a single UE within a coverage area or where a single UE is connected to the corresponding base station QQ412.

[0225] The telecommunications network QQ410 is itself connected to a host computer QQ430, which may be embodied as the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources within a server farm. The host computer QQ430 may be under the ownership or control of a service provider, or may be operated by or for a service provider. The connections QQ421 and QQ422 between the telecommunications network QQ410 and the host computer QQ430 may extend directly from the core network QQ414 to the host computer QQ430, or may be connected via an optional intermediate network QQ420. The intermediate network QQ420 may be one or a combination of a public, private, or hosted network, and the intermediate network QQ420 may be, if any, a backbone network or the Internet. Specifically, the intermediate network QQ420 may include two or more sub-networks (not shown).

[0226] The communication system of FIG. 18 enables connectivity between the connected UEs QQ491, QQ492 and the host computer QQ430 as a whole. That connectivity may be described as an over-the-top (OTT) connection QQ450. The host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and / or signaling via the OTT connection QQ450, using the access network QQ411, the core network QQ414, any intermediate network QQ420, and a possible further infrastructure (not shown) as intermediate steps. The OTT connection QQ450 can be transparent in the sense that participating communication devices along the path of the OTT connection QQ450 are not aware of the routing of the uplink communication and the downlink communication. For example, the base station QQ412 does not need to be notified of or does not require notification of the past routing of incoming downlink communication with data to be forwarded (e.g., handover) from the host computer QQ430 to the connected UE QQ491. Similarly, the base station QQ412 does not need to recognize the future routing of outgoing uplink communication from the UE QQ491 towards the host computer QQ430.

[0227] Figure 19: Host computer communicating with a user equipment via a base station over a partially wireless connection according to some embodiments

[0228] An exemplary implementation according to one embodiment of the UE, base station, and host computer discussed in the previous paragraph will now be described with reference to FIG. 19. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including a communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of different communication devices of communication system QQ500. Host computer QQ510 further comprises a processing circuit QQ518 that may have memory and / or processing capabilities. Specifically, processing circuit QQ518 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Host computer QQ510 further comprises software QQ511 stored within host computer QQ510 or accessible by host computer QQ510, the software QQ511 being executable by processing circuit QQ518. Software QQ511 includes a host application QQ512. Host application QQ512 may be operable to provide services to remote users such as UE QQ530 connected via an OTT connection QQ550 that terminates at UE QQ530 and host computer QQ510. During the provision of services to a remote user, host application QQ512 may provide user data transmitted using OTT connection QQ550.

[0229] The communication system QQ500 further includes a base station QQ520 provided in a telecommunication system, and the base station QQ520 comprises hardware QQ525 that enables communication with a host computer QQ510 and a UE QQ530. The hardware QQ525 includes a communication interface QQ526 for setting up and maintaining a wired or wireless connection with interfaces of different communication devices of the communication system QQ500, and may include a wireless interface QQ527 for setting up and maintaining at least a wireless connection QQ570 with a UE QQ530 located within a coverage area (not shown in FIG. 19) served by the base station QQ520. The communication interface QQ526 may be configured to facilitate a connection QQ560 to the host computer QQ510. The connection QQ560 may be direct or may pass through a core network of the telecommunication system (not shown in FIG. 19) and / or one or more intermediate networks outside the telecommunication system. In the illustrated embodiment, the hardware QQ525 of the base station QQ520 further includes a processing circuit QQ528 that may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instruction sets. The base station QQ520 further has software QQ521 stored internally or accessible via an external connection.

[0230] The communication system QQ500 further includes the UE QQ530 already mentioned. Its hardware QQ535 may include a radio interface QQ537 configured to set up and maintain a radio connection QQ570 with a base station that serves the coverage area where the UE QQ530 is located at that time. The hardware QQ535 of the UE QQ530 further includes a processing circuit QQ538 that may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instruction sets. The UE QQ530 further includes software QQ531 stored within or accessible by the UE QQ530 and executable by the processing circuit QQ538. The software QQ531 includes a client application QQ532. The client application QQ532 may be operable to provide services to human or non-human users via the UE QQ530 with the support of the host computer QQ510. In the host computer QQ510, the host application QQ512 to be executed may communicate with the client application QQ532 to be executed via the OTT connection QQ550 that terminates at the UE QQ530 and the host computer QQ510. During service provision to the user, the client application QQ532 may receive request data from the host application QQ512 and provide user data as a response to the request data. The OTT connection QQ550 may transfer both the request data and the user data. The client application QQ532 may interact with the user to generate the user data it provides.

[0231] Note that the host computer QQ510, base station QQ520, and UE QQ530 shown in FIG. 19 may be similar to or the same as one of the host computer QQ430, base stations QQ412a, QQ412b, QQ412c in FIG. 18, and one of the UEs QQ491, QQ492, respectively. That is to say, the internal operations of these entities may be as shown in FIG. 19, and independently thereof, the surrounding network topology may be the same as that in FIG. 18.

[0232] In FIG. 19, an OTT connection QQ550 is abstractly depicted to illustrate the communication between the host computer QQ510 and the UE QQ530 via the base station QQ520 without any explicit reference to any intermediate devices and the exact routing of messages through those devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to conceal the routing from the service provider operating the UE QQ530 or the host computer QQ510 or both. While the OTT connection QQ550 is active, the network infrastructure may further make decisions to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0233] The wireless connection QQ570 between the UE QQ530 and the base station QQ520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of the OTT services provided to the UE QQ530 using the OTT connection QQ550, and the wireless connection QQ570 forms the last segment thereof. 。

[0234] For the purpose of monitoring data rate, latency, and other factors improved by one or more embodiments, a measurement procedure may be provided. There may further be optional network functionality for reconfiguring the OTT connection QQ550 between the host computer QQ510 and the UE QQ530 in response to fluctuations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection QQ550 may be implemented in the software QQ511 and hardware QQ515 of the host computer QQ510, or the software QQ531 and hardware QQ535 of the UE QQ530, or both. In multiple embodiments, sensors (not shown) through which the OTT connection QQ550 passes may be deployed within or associated with the communication device, and those sensors may participate in the measurement procedure by supplying the numerical values of the monitoring results exemplified above or supplying the values of other physical quantities, and the quantities to be monitored may be calculated or estimated from them by the software QQ511, QQ531. The reconfiguration of the OTT connection QQ550 may include message format, retransmission settings, suitable routing, etc., and the reconfiguration may not affect the base station QQ520 and may be unknown or imperceptible to the base station QQ520. Such procedures and functionality may be known or in use in the art. In one embodiment, the measurement may include unique UE signaling that facilitates measurements such as throughput, propagation time, and latency by the host computer QQ510. The measurement may be implemented in such a way that the software QQ511 and QQ531 transmit messages that are specifically empty or "dummy" messages using the OTT connection QQ550 while monitoring propagation time, errors, etc.

[0235] Figure 20: Method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0236] FIG. 20 is a flowchart showing a method implemented in a communication system according to one embodiment. The communication system may include a host computer, a base station, and a UE as described with reference to FIGS. 18 and 19. For the sake of brevity of the present disclosure, only references to the figures of FIG. 20 will be included in this section. In step QQ610, the host computer provides user data. In sub-step QQ611 (which may be optional) of step QQ610, the host computer provides user data by executing a host application. In step QQ620, the host computer starts transmitting the user data to the UE that will carry it. In step QQ630 (which may be optional), the base station transmits the user data carried in the above transmission started by the host computer to the UE according to the teachings of the embodiments described throughout the present disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0237] FIG. 21: Method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0238] FIG. 21 is a flowchart showing a method implemented in a communication system according to one embodiment. The communication system may include a host computer, a base station, and a UE, as described with reference to FIGS. 18 and 19. For the sake of brevity of the present disclosure, only references to the figures of FIG. 21 will be included in this section. In step QQ710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step QQ720, the host computer starts transmitting the user data to the UE that carries the user data. The transmission may pass through the base station according to the teachings of the embodiments described throughout the present disclosure. In step QQ730 (which may be optional), the UE receives the user data carried in the above transmission.

[0239] FIG. 22: Method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0240] FIG. 22 is a flowchart showing a method implemented in a communication system according to one embodiment. The communication system may include a host computer, a base station, and a UE as described with reference to FIGS. 18 and 19. For the sake of brevity of the present disclosure, only references to the figures of FIG. 22 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In sub-step QQ821 (which may be optional) of step QQ820, the UE provides user data by executing a client application. In sub-step QQ811 (which may be optional) of step QQ810, the UE executes a client application that provides user data in reaction to receiving the input data provided by the host computer. During the provision of user data, the client application being executed may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, the UE starts transmitting the user data to the host computer in sub-step QQ830 (which may be optional). In step QQ840 of the method, the host computer receives the user data transmitted from the UE according to the teachings of the embodiments described throughout the present disclosure.

[0241] FIG. 23: A method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0242] FIG. 23 is a flowchart showing a method implemented in a communication system according to one embodiment. The communication system may include a host computer, a base station, and a UE, as described with reference to FIGS. 18 and 19. For the sake of brevity of the present disclosure, only references to the figures in FIG. 23 will be included in this section. In step QQ910 (which may be optional), according to the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station starts transmitting the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission started by the base station.

[0243] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of those functional units. Those functional units may be implemented via a processing circuit that may include one or more microprocessors or microcontrollers, and other digital hardware that may include a digital signal processor (DSP) and special purpose digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, and the memory may include one or more types of memory such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunication and / or data communication protocols, and instructions for performing one or more of the techniques described herein. In some embodiments, the processing circuit may be used to cause each functional unit to perform a function according to one or more embodiments.

[0244] The term "unit" may have its conventional meaning in the field of electronic devices, electrical devices, and / or electronic devices, and may include, for example, electrical circuits and / or electronic circuits, devices, modules, processors, memories, logic solid-state elements and / or discrete devices, computer programs, or instructions for performing respective tasks, procedures, calculations, outputs, and / or display functions, such as those described herein.

Claims

1. A method performed by a first core network node in a core network of a wireless communication system, wherein the first core network node is a session management function (SMF) node, the method comprising: Receiving a first request to establish a first protocol data unit (PDU) session between a user equipment (UE) and a user plane function in the core network (1102); Generating user plane (UP) security implementation information to be applied to the first PDU session (1104); Transmitting the UP security implementation information to a radio access network (RAN) node to establish the first PDU session (1106); Causing the second core network node to store the UP security implementation information for use in establishing subsequent PDU sessions for the UE as redundant PDU sessions for ultra-reliable low-latency communication (URLLC) (1108); and The second core network node is the SMF node, a policy control function (PCF) node, or a unified data management (UDM) function node.

2. The method according to claim 1, further comprising: Receiving a second request to establish a second PDU session between the UE and the user plane function in the core network (1110).

3. The method according to claim 2, wherein the second PDU session is established as the redundant PDU session for the URLLC.

4. The method according to claim 2 or 3, further comprising: Transmitting the UP security implementation information to the RAN node to establish the second PDU session (1112).

5. The method according to any one of claims 2 to 4, wherein the UP security implementation information is stored by the SMF node.

6. The method according to any one of claims 2 to 5, further comprising selecting a user plane function to terminate the second PDU session.

7. The method according to any one of claims 2 to 6, wherein the second PDU session is established for redundant data transmission with the first PDU session.

8. The method according to any one of claims 2 to 7, wherein the second PDU session is carried on a data radio bearer (DRB) established between the UE and the secondary node.

9. The method according to any one of claims 1 to 8, wherein the RAN node is a master node.

10. The method according to any one of claims 1 to 9, wherein the RAN node is a gNB or an ng-eNB.

11. The method according to any one of claims 1 to 10, wherein the first request is received from the UE.

12. A first core network node (300) that is a session management function (SMF) node, a processing circuit (306); a network interface (304) connected to the processing circuit; and a memory (308) connected to the processing circuit, wherein when executed by the processing circuit, the memory causes the first core network node to receive a first request for establishing a first protocol data unit (PDU) session between a user equipment (UE) and a user plane function in the core network (1102); generate user plane (UP) security enforcement information to be applied to the first PDU session (1104); transmit the UP security enforcement information to a radio access network (RAN) node to establish the first PDU session (1106); and store the UP security enforcement information in a second core network node for use when establishing a subsequent PDU session for the UE as a redundant PDU session for ultra-reliable low-latency communication (URLLC) (1108), wherein the second core network node is the SMF node, a policy control function (PCF) node, or a unified data management (UDM) function node. The first core network node.

13. The first core network node according to claim 12, wherein the first core network node is further configured to perform the operation according to any one of claims 2 to 11.

Images