Processing of session context
By requesting the release of signaling sessions to the user-plane function in a wireless communication network and retaining context information, the problem of signaling session transfer complexity between session managers is solved, and service continuity and signaling overhead are achieved. Effect.
Patent Information
- Application Number
- CN202411075777.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2019-06-17
- Filing Date
- 2020-04-30
- Publication Date
- 2024-11-08
AI Technical Summary
In wireless communication networks, the signaling session transfer process between session managers is complex, resulting in increased signaling overhead, increased processing complexity, and may affect backward compatibility and service continuity.
The session management function (SMF) requests the user plane function (UPF) to release the signaling session and instructs the UPF to retain the context information of the signaling session so that this information can be used when the session is re-established, avoiding the introduction of a special session modification process and maintaining services. Continuity and reduce signaling overhead.
By retaining the context information of the signaling session, UPF can optimize processing when the signaling session is re-established, reducing processing complexity, maintaining service continuity, and reducing signaling overhead, ensuring backward compatibility.
Smart Images

Figure CN118921705A_ABST
Abstract
Description
[0001] This application is a divisional application of the Chinese patent application “Processing of Session Context” with application number 202080045093.3 (filing date April 30, 2020). Background Art
[0002] The wireless communication network interconnects wireless devices to a data network (DN), such as the Internet. Interconnected in this manner, the wireless device can establish a protocol data unit (PDU) session with the DN. A session manager in the wireless communication network (e.g., a session management function SMF in a 5G network) manages the PDU session. However, at some point in the life cycle of a PDU session, the wireless communication network may need to transfer the responsibility for managing the PDU session from one session manager to another. This complicates the interaction of the session manager with the user plane entity (e.g., the user plane function UPF in a 5G network) that handles the user plane path of the PDU session.
[0003] In this regard, the initial session manager will have previously established a signaling session (e.g., an N4 session in a 5G network) with a user plane entity for communications associated with the device's PDU session. When session management responsibility is transferred to a new session manager, communications associated with the PDU session will need to occur via the signaling session established between the new session manager and the user plane entity. Enabling efficient re-establishment of the same signaling session with the new session manager rather than with the old session manager has proven to be complex, particularly in a manner that reduces signaling overhead, minimizes processing complexity, and / or maintains backward compatibility. For example, introducing a new process between the user plane entity and the session manager specifically for modifying the signaling session to account for the session manager transfer increases signaling overhead and processing complexity while jeopardizing backward compatibility. Furthermore, re-establishing the same signaling session in a manner that maintains service continuity has proven to be complex.
[0004] Similar challenges arise for wireless devices transitioning between idle mode and connected mode, which prompts deletion and establishment of signaling sessions between user plane entities and session managers. Summary of the invention
[0005] According to some embodiments of the present invention, a session management function (SMF) requests a user plane function (UPF) to release a signaling session (e.g., an N4 session) between the SMF and the UPF, but also indicates to the UPF that the signaling session will be reestablished, for example, by the same or different SMF. The indication may, for example, include control signaling included in a session release request or otherwise associated with a session release request. In any case, based on the indication, in some embodiments, the UPF retains information from the context of the signaling session regardless of the request to release the signaling session. The UPF may then utilize the retained information during the transition period between the request to release the signaling session and the reestablishment of the signaling session. The UPF may, for example, use the retained information to route or buffer data packets during the transition period, for example, in order to avoid packet loss or delay, and thereby maintain service continuity. Alternatively or additionally, the UPF utilizes the retained information to process or accelerate the reestablishment of the signaling session, for example, so that the reestablished signaling session has the same session identifier, the same Internet Protocol (IP) address, an updated data packet counter value, and the like.
[0006] Some embodiments thus use control signaling associated with session release to effectively implement signaling session reestablishment, for example to avoid introducing a dedicated session modification process. In doing so, some embodiments advantageously maintain service continuity, reduce signaling overhead, reduce the amount of stored state, minimize processing complexity, and / or maintain backward compatibility for interactions between SMF and UPF.
[0007] More specifically, the embodiments herein include in the Example " section, which is incorporated into this Summary of the Invention by reference. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 A wireless communication system in accordance with some embodiments is shown.
[0009] Figure 2 Other embodiments are shown in which the same SMF re-establishes the signaling session.
[0010] Figure 3 A method performed by a network device configured to implement a UPF is described.
[0011] Figure 4 A method performed by a network device configured to implement a first SMF is depicted.
[0012] Figure 5 A network device configured to implement a UPF according to one or more embodiments is shown.
[0013] Figure 6A network device configured to implement a first SMF according to one or more embodiments is shown.
[0014] Figure 7 A method for session management function (SMF) context transfer is shown.
[0015] Figure 8 Some embodiments of modified transfer processes are shown.
[0016] Fig. 9 SMF functionality according to some embodiments is shown.
[0017] Fig.10 The UPF functionality according to some embodiments is shown.
[0018] Fig.11 is a block diagram of a wireless network according to some embodiments;
[0019] Fig.12 is a block diagram of a user device according to some embodiments
[0020] Fig.13 is a block diagram of a virtualization environment according to some embodiments;
[0021] Fig.14 is a block diagram of a telecommunications network connected to a host computer via an intermediate network according to some embodiments;
[0022] Fig.15 is a block diagram of a host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments;
[0023] Fig.16 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;
[0024] Fig.17 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;
[0025] Fig.18 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; and
[0026] Fig.19 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. DETAILED DESCRIPTION
[0027] Figure 1A wireless communication system 10 (e.g., a 5G system) according to some embodiments is shown. The system 10 includes an access network (AN) 10A (e.g., a radio access network RAN) that provides access to wireless devices 12 (e.g., user equipment). The system 10 may also include a core network (CN) that interconnects the system 10 to a data network (DN) 14 (e.g., the Internet).
[0028] As the system 10 is interconnected to the DN 14, the wireless device 12 may establish a protocol data unit (PDU) session 16-1 with the DN 14. The PDU session 16-1 is a logical connection between the wireless device 12 and the DN 14 and may also be generally referred to as a packet session. Figure 1 A session management function (SMF) 18-1 (e.g., in the CN) configured to manage the PDU session 16-1 is shown. Session management may involve, for example, establishing, modifying, and / or releasing the PDU session 16-1. In some embodiments, the SMF 18-1 may also assign an Internet Protocol (IP) address to the wireless device 12 for the PDU session 16-1. Alternatively or additionally, the SMF 18-1 may select and control a user plane function (UPF) 20 to handle the user plane path of the PDU session 16-1 (and serve as an external PDU session point for interconnection with the DN 14). The UPF 20 in this role may be responsible for packet routing and forwarding for the PDU session 16-1, as well as packet inspection for quality of service (QoS) processing.
[0029] As part of serving in these roles for the PDU session 16-1, the SMF 18-1 and the UPF 20 establish a signaling session 22-1 between them for communications related to the PDU session 16-1. The signaling session 22-1 can be viewed as a relationship or association between the SMF 18-1 and the UPF 20, which is dedicated to supporting the signaling of the PDU session 16-1. The signaling session 22-1 can, for example, describe the processing of the user plane of the PDU session 16-1 in the UPF 20. In some embodiments where the system 10 is a 5G system, the signaling session 22-1 can be an N4 session established on the N4 interface between the UPF 20 and the SMF 18-1, wherein the N4 interface is a bridge between the control plane and the user plane, and is used for PDU session management and business steering to the UPF and PDU usage and control of event reporting toward the SMF. In any case, the UPF 20 and the SMF 18-1 each store a context 24-1 for the signaling session 24-1. The context 24-1 includes information for the signaling session 22-1, such as a session identifier 25 and / or an Internet Protocol (IP) address 27 for the PDU session 16-1 on the interface between the UPF 20 and the DN 14. In this regard, alternatively or additionally, the context 24-1 may include information identifying a radio-side tunnel between the UPF 20 and the (R)AN 10A for the PDU session 16-1 and / or a DN-side tunnel between the UPF 20 and the DN 14 for the PDU session 16-1. Alternatively or additionally, the context 24-1 may include policy rules regarding packet processing, forwarding, and usage reporting for the PDU session 16-1, for example, the rules may originate from a policy control function (PCF) not shown. Such policy rules may include, for example, packet inspection rules, forwarding action rules, QoS enforcement rules, usage reporting rules, buffering action rules, etc.
[0030] However, at some point, the system 10 triggers the SMF 18-1 to transfer the PDU session management responsibility for the wireless device 12 to the new SMF 18-2. This may occur, for example, due to the deactivation of the SMF 18-1. Regardless of the reason for its occurrence, the session management responsibility transfer can be achieved in the following manner: a new process is introduced for the SMF 18-1 to transfer the signaling session context 24-1 to the new SMF 18-2, and a new process is introduced for the SMF 18-1 to modify the context 24-1 at the UPF 20 so that the context 24-1 is associated with the new SMF 18-2 instead of the old SMF 18-1. This will avoid having to establish a new signaling session between the UPF 20 and the new SMF 18-2 from scratch. However, the new process will unnecessarily introduce signaling overhead, increase processing complexity, and jeopardize backward compatibility. Rather than introducing these complex new transfer / modification procedures, some embodiments advantageously enhance relatively simple procedures for session establishment and release in a manner that enables efficiency in signaling session transfer / modification without the associated complexity and backward compatibility issues.
[0031] According to some embodiments, for example, the SMF 18-1 sends a request 26 to the UPF 20 to release the signaling session 22-1 established between the UPF 20 and the SMF 18-1 for the PDU session 16-1. The request 26 to release the signaling session 22-1 is equivalent to a request to delete the signaling session context 24-1 at the UPF 20. In contrast, the new SMF 18-2 sends a request 28 to the UPF 20 to establish a new signaling session 22-2 between the UPF 20 and the SMF 18-2, i.e., for the new PDU session 16-2 between the wireless device 12 and the DN 14. The new signaling session 22-2 will have a new signaling session context 24-2 at the new SMF 18-2 and the UPF 20, respectively.
[0032] However, it is worth noting that, according to some embodiments, the SMF 18-1 sends to the UPF 20 specific control signaling 30, for example included in the request 26 to release the signaling session 22-1 or otherwise associated with the request 26. In some embodiments, the control signaling 30 indicates that the signaling session 22-1, the release of which is requested, will be re-established with the UPF 20, for example as a new signaling session 22-2 with a new SMF 18-2 that takes over responsibility for PDU session management for the wireless device 12. In this sense, the re-establishment of the signaling session 22-1 may mean that the signaling session 22-1 will be replaced by an upcoming new signaling session 22-2, which will have some similarities with the old signaling session 22-1. In one embodiment, for example, this means that the new signaling session context 24-2 will have at least some information in common with the old signaling session context 24-1. In some embodiments, the control signaling 30 may thereby effectively indicate or suggest to the UPF 20 that at least some information from the context 24-1 of the signaling session 22-1 whose release is requested may be utilized or reused to form the context 24-2 of the upcoming signaling session 22-2. Then, generally, the control signaling 30 may indicate that the signaling session 22-1 will be reestablished with the UPF 20, that a new signaling session 22-2 related to the old signaling session 22-1 will be established with the UPF 20, or that the UPF 20 will take some action (e.g., information retention) with respect to the signaling session 22-1.
[0033] In any case, based on the control signaling 30, in some embodiments, the UPF 20 at least temporarily retains at least some information from the signaling session context 24-1, regardless of the request 26 to release the signaling session 22-1. That is, unlike the immediate and complete deletion of the signaling session context 24-1 that would occur in the absence of the control signaling 30, the UPF 20 temporarily keeps storing at least some of the information in the signaling session context 24-1. Figure 1 The information 32 retained by the UPF 20 is shown, for example, to include a session identifier 24 identifying the signaling session 22-1 and an IP address for the PDU session 16-1 on an interface between the UPF 20 and the DN 14. Although not shown, alternatively or additionally, the retained information 32 may include information identifying a radio-side tunnel between the UPF 20 and a radio network node in the AN 10A and / or information identifying a DN-side tunnel between the UPF 20 and the DN 14. Regardless of the specific information retained, the UPF 20 may retain the information 32 until the signaling session 22-1 is reestablished, or until a threshold amount of time has passed to allow such reestablishment.
[0034] With at least some of the information 32 from the signaling session context 24-1 retained in this manner, the UPF 20 utilizes the information 32 to process the request 28 for a new signaling session 22-2 from the new SMF 18-2, according to some embodiments. The UPF 20 may determine, for example, by determining that one or more parameter values in the retained information 32 match one or more parameter values in the request 28, that the new signaling session 22-2 requested by the received request 28 will effectively reestablish the old signaling session 22-1. The parameter values may include, for example, a session ID, an IP address for the PDU session on the interface between the UPF 20 and the DN 14, and / or (one or more) tunnel identifiers for the radio side tunnel and / or the DN side tunnel for the PDU session. However, regardless of how the UPF 20 is implemented, in some embodiments, the UPF 20 may use the retained information 32 to process the reestablishment of the signaling session 22-1, for example as a new signaling session 22-2 with the new SMF 18-2. For example, UPF 20 may efficiently form a new signaling session context 24-2 from the retained information 32, rather than forming a new signaling session context 24-2 from scratch. Figure 1 As shown, the new signaling session 22-2 may then be identified by the same session identifier 25 as the old signaling session 22-1, and / or be associated with the same PDU session IP address 28 as the old signaling session 22-1. Alternatively or additionally, the UPF 20 may form the new signaling session context 24-2 to have the same (one or more) packet counter values as the old signaling session context 24-1, for example, these packet counter values may even be updated in some embodiments to account for any packets forwarded / buffered during the transition period between the old SMF 18-1 releasing the signaling session 22-1 and the new SMF 18-2 reestablishing the signaling session 22-1 as a new signaling session 22-2.
[0035] Alternatively or additionally, in this regard, according to some embodiments, the UPF 20 may otherwise utilize the retained information 32 during a transition period between the old SMF 18-1 releasing the signaling session 22-1 and the new SMF 18-2 reestablishing the signaling session 22-1 as a new signaling session 22-2. For example, the UPF 20 may use the retained information 32 to process packets received by the UPF 20 during the transition period (i.e., after receiving the release request 26 but before receiving the establishment request 28). The UPF 20 may, for example, use the retained information 32 to route or forward packets. For example, where the retained information 32 includes information identifying a radio side tunnel for the PDU session 16-1, the UPF 20 may forward the received packet in the radio side tunnel instead of dropping or delaying the packet because the signaling session 22-1 or the PDU session 16-1 is not established. Similarly, where the retained information 32 includes information identifying the DN-side tunnel for the PDU session 16-1, the UPF 20 may forward the received packet in the DN-side tunnel.
[0036] Alternatively or additionally, the UPF 20 may buffer packets until the signaling session is reestablished. Such buffering may thereby mark packets as being associated with the old signaling session 22-1, the old PDU session 16-1, the upcoming signaling session 22-2, and / or the upcoming PDU session 16-2 so that once reestablishment occurs, the packets may be forwarded appropriately.
[0037] According to one embodiment in a 5G system, for example, the UPF 20 processes (e.g., buffers or forwards) IP packets having a specific N6 IP address associated with the old signaling session 22-1. If a new signaling session 22-2 is established with the same N6 IP address, any buffered packets are released, and / or any packets that have been forwarded during the transition period according to the retained information 32 are counted in the packet counter of the new signaling session.
[0038] Some embodiments thus use the control signaling 30 associated with session release to effectively implement signaling session re-establishment to avoid introducing a dedicated session modification process. In doing so, some embodiments advantageously maintain service continuity, reduce signaling overhead, minimize processing complexity, and / or maintain backward compatibility for the interaction between SMF and UPF 20.
[0039] although Figure 1 The new SMF 18-2 is shown to re-establish the signalling session 22-1 as a new signalling session 22-2, however, Figure 2Other embodiments are shown where the same SMF 18-1 is the entity that reestablishes the signaling session 22-1 as a new signaling session 22-2. This may occur, for example, where the signaling session 22-1 is related to a cellular Internet of Things (cIoT) session that is "suspended" while the wireless device 12 is operating in sleep mode. Thus, the UPF 20 may be as described above for Figure 1 The UPF 20 may operate and function as described, regardless of whether the signaling session 22-1 is reestablished by a different SMF 18-2 or by the same SMF 18-1 with which the signaling session 22-1 has been established. For example, the UPF 20 may retain the context information 32 as described above for processing packets during the transition between the signaling session 22-1 being released and reestablished and / or for forming a new signaling session context 24-2. According to some embodiments, then, the control signaling 30 as described above may or may not specify with which SMF the signaling session 22-1 is to be reestablished, for example, because the UPF 20 behaves the same in either case. However, in other embodiments, the control signaling 30 does specify the SMF with which the signaling session 22-1 is to be reestablished, so that the UPF 20 may operate in different ways depending on whether the signaling session 22-1 is to be reestablished with the same SMF or with a different SMF.
[0040] according to Figure 2 In a 5G example of an embodiment in FIG. 1 , when the wireless device 12 is operating in a sleep state, the UPF 20 effectively refreshes the N4 rules in the signaling session context 24-1 associated with the cIoT session based on the control signaling 30. When the wireless device 12 returns to an active / awake state, the SMF 18-1 then sends the N4 rules again. These and other embodiments can thereby reduce the computational and storage requirements of the UPF 20 because the UPF 20 needs to maintain a smaller amount of state for the signaling session 22-1 when the device 12 is operating in a sleep state.
[0041] In view of the above modifications and changes, Figure 3 A method is depicted according to certain embodiments performed by a network device configured to implement a UPF 20 that handles a user plane path of a PDU session 16-1 between a wireless device 12 and a DN 14. The method includes receiving a request 26 from a first SMF 18-1 configured to manage the PDU session 16-1 to release a signaling session 22-1 established between the UPF 20 and the first SMF 18-1 for the PDU session 16-1 (block WW100). The method also includes receiving control signaling 30 from the first SMF 18-1 indicating that the signaling session 22-1 will be reestablished with the UPF 20 (block WW110). In some embodiments, the control signaling 30 is included in the request 26 or otherwise associated with the request 26.
[0042] In some embodiments, the method further includes retaining information 32 from the context 24-1 based on the control signaling 30, regardless of the request 26 to release the signaling session 22-1 (block WW120). In this case, the method may also include receiving a packet at the UPF 20, and processing the packet using the retained information 32 from the context 24-1 for the signaling session 22-1 (block WW130). Alternatively or additionally, the method may include reestablishing the signaling session using the retained information 32 from the context 24-1 (block WW140).
[0043] Figure 4 A method performed by a network device configured to implement a first SMF 18-1 that manages a PDU 16-1 session between a wireless device 12 and a DN 14 is depicted according to other specific embodiments. The method includes sending a request 26 from the first SMF 18-1 to a UPF 20 that handles a user plane path of the PDU session 16-1 to release a signaling session 22-1 established between the UPF 20 and the first SMF 18-1 for the PDU session 16-1 (block WW200). The method also includes sending control signaling 30 from the first SMF 18-1 to the UPF 20 indicating that the signaling session 22-1 is to be reestablished (block WW210). In some embodiments, the control signaling 30 is included in the request 26 or otherwise associated with the request 26.
[0044] In some embodiments, control signaling 30 is sent based on receiving a transfer request requesting the first SMF to transfer the session management context at the first SMF for the PDU session to the second SMF. In other embodiments, control signaling 30 is sent based on determining that the wireless device 12 is operating in a sleep state.
[0045] Note that the above-mentioned device can perform the method and any other processing of this article by implementing any functional device, module, unit or circuit. In one embodiment, for example, the device includes a corresponding circuit or circuit system configured to perform the steps shown in the method diagram. In this regard, the circuit or circuit system may include a circuit dedicated to performing certain functional processing and / or one or more microprocessors combined with a memory. For example, the circuit system may include one or more microprocessors or microcontrollers, and other digital hardware (which may include a digital signal processor (DSP), dedicated digital logic, etc.). The processing circuit may be configured to execute a program code stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, etc. In several embodiments, the program code stored in the memory may include program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In an embodiment using a memory, the memory stores a program code, which executes the technology described herein when executed by one or more processors.
[0046] Figure 5 For example, a network device YY100 configured to implement the UPF 20 as implemented according to one or more embodiments is shown. As shown, the network device YY100 includes a processing circuit YY110 and a communication circuit YY120. The communication circuit YY120 is configured to send and / or receive information to and / or from one or more other nodes, for example, via any communication technology. The processing circuit YY110 is configured to perform, for example, by executing instructions stored in a memory YY130. Figure 3 In this regard, the processing circuit YY110 may implement certain functional devices, units or modules.
[0047] Figure 6 A network device YY200 is shown that is configured to implement a first SMF 18-1 as implemented according to one or more embodiments. As shown, the network node YY200 includes a processing circuit YY210 and a communication circuit YY220. The communication circuit YY220 is configured to send and / or receive information to and / or from one or more other nodes, for example via any communication technology. The processing circuit YY210 is configured to perform, for example, by executing instructions stored in a memory YY230. Figure 4 In this regard, the processing circuit YY210 may implement certain functional devices, units or modules.
[0048] Those skilled in the art will also understand that the embodiments herein also include corresponding computer programs.
[0049] The computer program includes instructions that, when executed on at least one processor of a device, cause the device to perform any corresponding processing described above. In this regard, the computer program may include one or more code modules corresponding to the above-mentioned means or units.
[0050] The embodiment also includes a carrier embodying such a computer program. The carrier may include one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.
[0051] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer-readable (storage or recording) medium and including instructions that, when executed by a processor of a device, cause the device to perform as described above.
[0052] The embodiment also includes a computer program product, which includes a program code portion, and when the computer program product is executed by a computing device, the program code portion is used to perform the steps of any embodiment in this document. The computer program product can be stored on a computer-readable recording medium.
[0053] Note that while some embodiments of the present invention have been described with respect to a session management function (SMF), for example in the context of a 5G system, the role of the described SMF may be implemented by any physical, logical or functional node or entity configured to manage PDU sessions 16. When the above description refers to an SMF, the description may be generalized to any session manager including a node or entity configured to manage PDU sessions 16.
[0054] Similarly, although some embodiments herein have been described with respect to a user plane function (UPF), for example in the context of a 5G system, the role of the described UPF may be implemented by any physical, logical or functional node or entity configured to handle the user plane path of a PDU session 16. When the above description refers to a UPF, the description may be generalized to any user plane node or entity configured to handle the user plane path of a PDU session 16.
[0055] Additional embodiments will now be described.For purposes of illustration, at least some of these embodiments may be described as applicable to certain contexts and / or wireless network types, however, these embodiments are similarly applicable to other contexts and / or wireless network types not explicitly described.
[0056] The next generation (5G) network architecture is defined in the new 3GPP Rel 15. See 3GPP TS 23.502, V16.0.2, Procedures for 5G Systems; Stage 2. The key aspect in which 3GPP networks will differ from Release 15 onwards is that the core network (CN) architecture is primarily built around the service-based architecture (SBA) paradigm. That is, there will be network domains (basically the core network (CN)) where different functional components are defined as services, which are self-contained functions that can be changed and modified in an isolated manner (without affecting other functions).
[0057] Services in 5G CN (5GC) will likely be built in a stateless manner, meaning that business logic and data context will be separated. This means that services store their context in an external proprietary database. This will enable various cloud infrastructure features, such as auto-scaling or auto-repair.
[0058] In addition to this, services will be deployed as part of NFs (network functions), and multiple NF instances can be deployed in a Set, as long as these instances have access to the same context data. The operator's intention is to deploy at least two different Sets of the same NF type, each set possibly from a different vendor, and then there is an opportunity to transfer some information related to the context stored in Set 1 (e.g., the related User Equipment (UE) or / and Protocol Data Unit (PDU) session) to Set 2, with the intention of continuing to process the context in Set 2. The context data that needs to be transferred may vary, but in any case it should be sufficient to allow the target Set (Set 2) to reconstruct a processing state that is as close to that in Set 2; that is, to allow the target to recover the internal business logic state in order to continue processing.
[0059] NF may include, for example, a session management function (SMF) responsible for session management, an access and mobility function (AMF) responsible for mobility management, and a user plane function (UPF) responsible for processing the user plane path. SMF and UPF may interact through the N4 interface. UPF may interact with the access network (e.g., RAN) through the N3 interface and interact with the data network (DN) through the N6 interface.
[0060] A method for session management function (SMF) context transfer is as follows Figure 7 See also 3GPP TS 23.502 CR1325: SMF Context Transfer, S2-1906744.
[0061] 1. Session Management (SM) context transfer, e.g. triggered by Operation and Maintenance (OAM), includes the User Permanent Identifier (SUPI), PDU Session ID and new SMF ID.
[0062] 2. Nsmf_PDUSession_StatusNotify (SMF transfer indication, new SMF ID) from old SMF to AMF,
[0063] 3. The Access and Mobility Function (AMF) waits until the UE becomes IDLE or the Radio Resource Control (RRC) is inactive.
[0064] 4.AMF uses the new SMF ID to select a new SMF and sends a Nsmf_PDU_Session_CreateSMContext request (PDU session ID, SM context ID, UE location information, access type, radio access technology type, operation type, SMF transfer information). Use the same PDU session ID received in step 1.
[0065] 5. Nsmf_PDUSessionContextRequest request (SM context type, SM context ID, SMF transfer indication) from the new SMF to the old SMF.
[0066] 6. The old SMF releases the N4 session.
[0067] 7. Nsmf_PDUSessionContextRequest Response (SM Context) from old SMF to new SMF. In case the PDU session is of IPv4, IPv6 or IPv4v6 type, the SM Context includes (one or more) IP addresses, or in case the PDU session type is Ethernet, the SM Context includes (one or more) Ethernet MAC addresses.
[0068] 8. [Conditional] If a dynamic PCC is used for the PDU session, the new SMF establishes a new policy association to the PCF.
[0069] 9. The new SMF establishes the N4 session, using the parameters from step 7 and step 8 (if applicable).
[0070] 10. From new SMF to AMF: Nsmf_PDU_Session_CreateSMContext response.
[0071] 11. The new SMF is registered to the Unified Data Management (UDM),
[0072] 12. New SMF subscription for UE subscription changes.
[0073] 13. [Conditional] The old SMF deletes its policy association with the PCF (triggered by step 7). Any changes to the QoS rules need to be sent to the UE when it becomes active. After step 13 (or step 7 if there is no policy association), the old SMF may release any internal resources used for the PDU Session.
[0074] There are certain challenges. Figure 7 The problem with the solution in is that when the user plane (UP) is not established between the UE and the UPF, there is a period of time (between the old SMF deleting the N4 session and the new SMF establishing the N4 session, i.e., Figure 7 In some cases, this can lead to service continuity issues.
[0075] For example, in one case, one or more packets from the data network (DN) destined for a UE in any state (e.g., an Internet server attempting to communicate with the UE) arrive at the UPF during this time period. Since there is no N3 connection established for the given IP address (or state for an idle UE), the UPF will discard the packets. In many cases, this can result in failure of server connection establishment.
[0076] In another case, a UE that was in RRC INACTIVE mode becomes active and sends a packet. The radio base station forwards the packet to the UPF, but the UPF has deleted the downlink tunnel, so it will not recognize the packet as coming from a valid PDU session and will discard the packet.
[0077] In another case, for example, when the old SMF needs to be deactivated, it may be necessary to initiate a context transfer, even if the UE is in the ACTIVE state. In this case, all packets sent by the UE and directed to the UE will be lost.
[0078] One solution may be to optimize or change steps 6 and 9 so that they modify the N4 session. However, this solution would have the following consequences. A solution to change the N4 association from the old SMF to the new SMF would require updated N4 communications, for example in the form of a new type of N4 session modification signaling that enables the change of the N4 association from the old SMF to the new SMF. Furthermore, this solution would require new UPF functionality in Release 16, increasing the complexity of the deployment. Furthermore, complex N4 session related state transfers would be required between the old and new SMFs.
[0079] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Some embodiments propose enhancements to the SMF transfer process that are still based on the old SMF releasing the N4 session and the new SMF re-establishing it, but may produce similar benefits as if the N4 session had not been released. In some embodiments, for example, the old SMF sends a flag in the N4 session release message indicating that the session is being transferred and / or that the session will be re-established soon. Based on this, the enhanced UPF will optimize the user plane processing during context transfer by maintaining some of its internal states related to the N4 session.
[0080] Some embodiments thus propose enhanced logic in the SMF (to add a flag in the N4 session release message) and enhanced logic in the UPF to act on the flag to minimize service degradation or interruption during the PDU session context transfer. Some embodiments do this by maintaining the N4 session (and N4 association) release process but adding a re-establishment notification to the UPF in the N4 session release request from the old SMF. Based on this, the UPF can temporarily keep some information related to the N4 session to optimize packet processing until the new SMF re-establishes the N4 session. Note that this solution can provide backward compatibility for the UPF.
[0081] Certain embodiments may provide one or more of the following technical advantages. Some embodiments may minimize the impact on UP session performance during the context transfer process. Alternatively or additionally, some embodiments represent minimal complexity increase over current approaches, unlike approaches that would move N4 session associations from one SMF to another. Furthermore, some embodiments are backward compatible with UPFs from previous versions, e.g., a legacy UPF would ignore the new flags and its actions would correspond to those in the current process.
[0082] Some embodiments provide for Figure 7 The transfer process is modified as follows.
[0083] Modified step 6. The old SMF releases the N4 session with the UPF by sending an N4 Session Release Request (N4 Session ID), where a new ToBeReestablished flag is added to the message, notifying the UPF about the expected re-establishment of the N4 session for the same PDU session. An alternative approach is to add the ToBeReestablished flag in the GTP-U extension header of the Packet Forwarding Control Protocol (PFCP) tunnel. See 3GPP TS29.244, V15.5.0, Interface between Control Plane and User Plane Nodes. In some embodiments, the flag is added as an optional information element in the Packet Forwarding Control Protocol (PFCP) communication. This can be done, for example, with a PFCP associated update message. In this case, the SMF can send an N4 Session Update with the required flag before sending the N4 Session Release. But in other embodiments, the SMF adds the flag to the N4 Session Release message. In these and other alternatives, the traditional UPF ignores the new attributes and processes the N4 message normally. All N4 session-related information is deleted in the old SMF.
[0084] Based on the received flag, the UPF may temporarily retain some information related to the N4 session to optimize packet processing until the new SMF re-establishes the N4 session. For example, in the problem scenario listed above, the following UPF functions may be applied. In the event that one or more packets from the DN destined for a UE in any state arrive at the UPF, the UPF may forward or buffer the packets. Specifically, if the UE state is active on the UPF side (i.e., there is an N3 interface), the packets are forwarded to the corresponding RBS in the corresponding N3 tunnel. If the UE state is idle, the UPF buffers the received packets until a new N4 session is established with the new SMF ( Figure 7 Then, UPF initiates UE paging and service request through the new SMF.
[0085] In the event that a UE that was originally in an RRC inactive state becomes active and sends packets, the UPF according to some embodiments forwards the IP packets as if it were an active N4 session for that UE.
[0086] In the case where a UE in active state sends a packet (context transfer must be initiated when the UE is in active state), the UPF may apply the same processing as described above.
[0087] Note that other alternative processes may be applied. For example, if it is not allowed for the UPF to forward packets without an active N4 session for a given PDU session, the UPF may instead apply buffering of data for all of the above cases and release the buffered packets to the destination when the N4 session is reestablished. This also minimizes service disruption since no packets will be lost.
[0088] Modified step 9. The new SMF establishes a new N4 session with the UPF. The parameters in step 7 and step 8 (if applicable) may be used. The UPF may use information from the previous session to optimize the establishment of the new N4 session. However, after the new N4 session is established, all information related to the previous N4 session is deleted from the UPF.
[0089] Figure 8 Some embodiments of the modified transfer process are presented.
[0090] 1. SM context transfer is triggered by OAM, for example, including SUPI, PDU session ID and new SMF ID.
[0091] 2. [Conditional – depends on current subscription] Old SMF subscribes to events (Namf_EventExposure_Subscribe) when UE state becomes idle or RRC inactive.
[0092] 3. [Conditional - event dependent] The AMF detects that the monitored event occurs and sends an event report to the old SMF via the Namf_EventExposure_Notify message.
[0093] 4. From old SMF to AMF: Nsmf_PDUSession_StatusNotify (SMF transfer indication, new SMF ID)
[0094] 5.AMF selects a new SMF using the new SMF ID and sends a Nsmf_PDU_Session_CreateSMContext request (PDU session ID, SM context ID, UE location information, access type, RAT type, operation type, SMF transfer information). Use the same PDU session ID received in step 4.
[0095] 6. From the new SMF to the old SMF: Nsmf_PDUSessionContextRequest request (SM context type, SM context ID, SMF transfer indication).
[0096] 7. The old SMF releases the N4 session with the UPF by sending a flag (ToBeReestablished) to notify the UPF about the expected re-establishment of the N4 session for the same PDU session. Based on this, the UPF can temporarily keep some information related to the N4 session to optimize packet processing until the new SMF re-establishes the N4 session. All N4 session related information is deleted in the old SMF.
[0097] 8. From old SMF to new SMF: Nsmf_PDUSessionContextRequest response (SM context). In case the PDU session is of type IPv4, IPv6 or IPv4v6, the SM context includes (one or more) IP addresses, or in case the PDU session type is Ethernet and the UPF is selected by the new SMF, the SM context includes (one or more) Ethernet MAC addresses.
[0098] 9. [Conditional] If a dynamic PCC is used for the PDU session, the new SMF establishes a new policy association to the PCF.
[0099] 10. The new SMF performs a complete re-establishment of the session (IMS signalling, online charging, etc.) and establishes a new N4 session with the UPF. Parameters from step 8 and step 9 (if applicable) are used. All information related to the previous N4 session is deleted from the UPF.
[0100] 11. From new SMF to AMF: Nsmf_PDU_Session_CreateSMContext response
[0101] 12. Register the new SMF to UDM,
[0102] 13. New SMF subscription for UE subscription changes.
[0103] 14. [Conditional] The old SMF deletes its policy association with the PCF (triggered by step 7). Any changes to the QoS rules need to be sent to the UE when the UE becomes active. After step 14 (or step 8 if there is no policy association), the old SMF may release any internal resources used for the PDU Session.
[0104] Notice, Figure 8The context-specific transfer process in can be between different sets of SMFs that support the same DNN / S-NSSAI pair for the SM context (i.e., SMF context). Also note that in some embodiments, in the case of dynamic IP address allocation (IPv4 address and / or IPv6 prefix), control of the (one or more) IP addresses allocated by the old SMF is transferred to the new SMF through the O&M process. When the transfer is complete, the new SMF has full control of the associated (one or more) IP addresses. In addition, if the UPF has an IP presence point from the DNN, the same UPF is used.
[0105] Fig. 9 SMF functionality according to some embodiments is shown.
[0106] Fig.10 The UPF functionality according to some embodiments is shown.
[0107] The SMF and UPF functions proposed in steps 6 and 9 are shown in Fig. 9 and Fig.10 in the flow chart.
[0108] Note that some embodiments enable separation of service logic from data, which helps apply cloud-native design principles to services in the SBA domain.
[0109] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Fig.11 For simplicity, Fig.11 The wireless network of only depicts network QQ106, network nodes QQ160 and QQ160b, and WD QQ110, QQ110b and QQ110c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline), a service provider, or any other network node or terminal device. In the components shown, network node QQ160 and wireless device (WD) QQ110 are depicted with additional details. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by the wireless network or services provided via the wireless network.
[0110] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-wave, and / or ZigBee standards.
[0111] The network QQ106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.
[0112] The network node QQ160 and WD QQ110 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals via wired or wireless connections.
[0113] As used herein, a network node refers to a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR node Bs (gNBs)). Base stations can be classified based on the amount of coverage provided by the base stations (or in other words, their transmit power levels), and then they can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node may also 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) (sometimes also referred to as a remote radio head (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multi-standard radio (MSR) devices such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and / or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, a network node may represent any suitable device (or group of devices) that is capable of, configured to, arranged to, and / or operable to enable a wireless device to access a wireless network and / or to provide access to a wireless network to a wireless device or to provide a certain service to a wireless device that has accessed a wireless network.
[0114] exist Fig.11 In the embodiment, the network node QQ160 includes a processing circuit QQ170, a device readable medium QQ180, an interface QQ190, an auxiliary device QQ184, a power supply QQ186, a power supply circuit QQ187, and an antenna QQ162. Fig.11The network node QQ160 shown in the example wireless network may represent a device including a combination of the illustrated hardware components, however, other embodiments may include network nodes having different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node QQ160 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up a single illustrated component (e.g., the device readable medium QQ180 may include multiple separate hard drives and multiple RAM modules).
[0115] Similarly, the network node QQ160 can be composed of multiple physically separated components (e.g., Node B components and RNC components, or BTS components and BSC components, etc.), each of which can have its own corresponding components. In some cases where the network node QQ160 includes multiple separated components (e.g., BTS and BSC components), one or more separated components can be shared between several network nodes. For example, a single RNC can control multiple Node Bs. In this case, each unique Node B and RNC pair can be regarded as a single separated network node in some cases. In some embodiments, the network node QQ160 can be configured to support multiple radio access technologies (RATs). In such an embodiment, some components can be copied (e.g., a separate device-readable medium QQ180 for different RATs), and some components can be reused (e.g., the same antenna QQ162 can be shared by RATs). The network node QQ160 can also include multiple groups of various illustrated components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi or Bluetooth wireless technologies) integrated into the network node QQ160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node QQ 160 .
[0116] The processing circuit QQ170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by the network node. The operations performed by the processing circuit QQ170 may include: processing information acquired by the processing circuit QQ170 by, for example, converting the acquired information into other information, comparing the acquired information or the converted information with 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 determination as a result of the processing.
[0117] The processing circuit QQ170 may include 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 any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide network node QQ160 functionality alone or in conjunction with other network node QQ160 components (e.g., 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 a chip (SOC).
[0118] In some embodiments, the processing circuitry QQ170 may include one or more of a radio frequency (RF) transceiver circuitry QQ172 and a baseband processing circuitry QQ174. In some embodiments, the radio frequency (RF) transceiver circuitry QQ172 and the baseband processing circuitry QQ174 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of the RF transceiver circuitry QQ172 and the baseband processing circuitry QQ174 may be on the same chip or chipset, board, or unit.
[0119] In certain embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB or other such network device may be performed by a processing circuit QQ170 executing instructions stored on a device-readable medium QQ180 or a memory within the processing circuit QQ170. In alternative embodiments, some or all of the functions may be provided by the processing circuit QQ170 without the need to perform instructions stored on a separate or discrete device-readable medium, such as in a hard-wired manner. In any of those embodiments, whether or not instructions stored on a device-readable storage medium are executed, the processing circuit QQ170 may be configured to perform the described functions. The benefits provided by such functions are not limited to the processing circuit QQ170 or other components of the network node QQ160 alone, but are enjoyed by the network node QQ160 and / or generally by end users and wireless networks as a whole.
[0120] The device-readable medium QQ180 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, 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 disk (CD), or digital video disk (DVD)), and / or any other volatile or non-volatile, non-temporary device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by the processing circuit QQ170. The device-readable medium QQ180 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or one or more of other instructions that can be executed by the processing circuit QQ170 and utilized by the network node QQ160. The device-readable medium QQ180 may be used to store any calculations performed by the processing circuit QQ170 and / or any data received via the interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
[0121] Interface QQ190 is used for wired or wireless communication of signaling and / or data between network node QQ160, network QQ106 and / or WD QQ110. As shown, interface QQ190 includes (one or more) ports / terminals QQ194 for sending and receiving data to and from network QQ106, for example, by wired connection. Interface QQ190 also includes a radio front-end circuit QQ192 that can be coupled to antenna QQ162 or is a part of antenna QQ162 in some embodiments. Radio front-end circuit QQ192 includes filter QQ198 and amplifier QQ196. Radio front-end circuit QQ192 can be connected to antenna QQ162 and processing circuit QQ170. Radio front-end circuit QQ192 can be configured to adjust the signal communicated between antenna QQ162 and processing circuit QQ170. Radio front-end circuit QQ192 can receive digital data to be sent to other network nodes or WDs via wireless connection. The radio front end circuit QQ192 may use a combination of filters QQ198 and / or amplifiers QQ196 to convert the digital data into a radio signal having appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect the radio signal, which is then converted into digital data by the radio front end circuit QQ192. The digital data may be passed to the processing circuit QQ170. In other embodiments, the interface may include different components and / or different combinations of components.
[0122] In some alternative embodiments, the network node QQ160 may not include a separate radio front end circuit QQ192, instead the processing circuit QQ170 may include the radio front end circuit and may be connected to the antenna QQ162 without the separate radio front end circuit QQ192. Similarly, in some embodiments, all or some of the RF transceiver circuit QQ172 may be considered part of the interface QQ190. In other embodiments, the interface QQ190 may include one or more ports or terminals QQ194, the radio front end circuit QQ192, and the RF transceiver circuit QQ172 as part of a radio unit (not shown), and the interface QQ190 may communicate with the baseband processing circuit QQ174, which is part of the digital unit (not shown).
[0123] Antenna QQ162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna QQ162 may be coupled to the radio front-end circuit QQ192 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna QQ162 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from a device within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, using more than one antenna may be referred to as MIMO. In some embodiments, antenna QQ162 may be separated from network node QQ160 and may be connected to network node QQ160 via an interface or port.
[0124] Antenna QQ162, interface QQ190 and / or processing circuit QQ170 can be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna QQ162, interface QQ190 and / or processing circuit QQ170 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.
[0125] The power circuit QQ187 may include or be coupled to a power management circuit and is configured to provide power to the components of the network node QQ160 to perform the functions described herein. The power circuit QQ187 may receive power from the power supply QQ186. The power supply QQ186 and / or the power circuit QQ187 may be configured to provide power to the various components of the network node QQ160 in a form suitable for the various components (e.g., at the voltage and current levels required by each corresponding component). The power supply QQ186 may be included in the power circuit QQ187 and / or the network node QQ160 or outside thereof. For example, the network node QQ160 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source provides power to the power circuit QQ187. As another example, the power supply QQ186 may include a power source in the form of a battery or a battery pack, which is connected to or integrated in the power circuit QQ187. If the external power supply fails, the battery can provide backup power. Other types of power supplies, such as photovoltaic devices, may also be used.
[0126] Alternative embodiments of network node QQ 160 may include, in addition to Fig.11 Additional components beyond those shown may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node QQ 160 may include a user interface device to allow information to be input into the network node QQ 160 and to allow information to be output from the network node QQ 160. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node QQ 160.
[0127] As used herein, a wireless device (WD) refers to a device that can, is configured to, is arranged to and / or is operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with a user equipment (UE) in this article. Wireless communication may involve using electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network according to a predetermined schedule when triggered by an internal or external event or in response to a request from a network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop computer built-in devices (LEEs), laptop computer installation devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication (e.g., by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X)), and in this case can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. WD as described above can represent an endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, the WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
[0128] 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 supply circuit QQ137. The WD QQ110 may include multiple groups of one or more of the components shown for different wireless technologies supported by the WD QQ110 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX, or Bluetooth wireless technologies, to name a few). These wireless technologies may be integrated into the same or different chips or chipsets as other components within the WD QQ110.
[0129] Antenna QQ111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separated from WD QQ110 and may be connected to WD QQ110 via an interface or port. Antenna QQ111, interface QQ114, and / or processing circuit QQ120 may be configured to perform any receiving or transmitting operation described herein as being performed by WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the radio front-end circuit and / or antenna QQ111 may be considered an interface.
[0130] As shown, the interface QQ114 includes a radio front-end circuit QQ112 and an antenna QQ111. The radio front-end circuit QQ112 includes one or more filters QQ118 and an amplifier QQ116. The radio front-end circuit QQ112 is connected to the antenna QQ111 and the processing circuit QQ120, and is configured to adjust the signal transmitted between the antenna QQ111 and the processing circuit QQ120. The radio front-end circuit QQ112 may be coupled to the antenna QQ111 or as part of the antenna QQ111. In some embodiments, the WD QQ110 may not include a separate radio front-end circuit QQ112; instead, the processing circuit QQ120 may include a radio 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 as part of the interface QQ114. The radio front-end circuit QQ112 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit QQ112 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters QQ118 and / or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect the radio signal, which is then converted into digital data by radio front-end circuit QQ112. The digital data may be passed to processing circuit QQ120. In other embodiments, the interface may include different components and / or different combinations of components.
[0131] The processing circuit QQ120 may include 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 any other suitable computing device, resource, or combination of hardware, software and / or encoded logic, which is operable to provide alone or in combination with other WDQQ110 components (e.g., device readable medium QQ130, WDQQ110 functions). Such functions may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit QQ120 may execute instructions stored in the device readable medium QQ130 or in a memory within the processing circuit QQ120 to provide the functions disclosed herein.
[0132] As shown, 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 some embodiments, the processing circuit QQ120 of the WD QQ110 may include a SOC. In some embodiments, the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit QQ124 and the application processing circuit QQ126 may be combined into one chip or chipset, and the RF transceiver circuit QQ122 may be on a separate chip or chipset. In yet another alternative embodiment, part or all of the RF transceiver circuit QQ122 and the baseband processing circuit QQ124 may be on the same chip or chipset, and the application processing circuit QQ126 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit QQ122, baseband processing circuit QQ124, and application processing circuit QQ126 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit QQ122 may be part of the interface QQ114. The RF transceiver circuit QQ122 may condition the RF signal for the processing circuit QQ120.
[0133] In some embodiments, some or all of the functions described herein as being performed by WD may be provided by processing circuit QQ120 executing instructions stored on device-readable medium QQ130, which may be a computer-readable storage medium in some embodiments. In alternative embodiments, some or all of the functions may be provided by processing circuit QQ120 without the need to execute instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those specific embodiments, processing circuit QQ120 may be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to separate processing circuit QQ120 or other components of WD QQ110, but may also be enjoyed by WD QQ110 and / or end users and wireless networks as a whole.
[0134] Processing circuit QQ120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by the WD. Such operations performed by processing circuit QQ120 may include: processing information obtained by processing circuit QQ120, such as by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD QQ110, and / or performing one or more operations based on the obtained information or the converted information; and making a determination as a result of the processing.
[0135] The device-readable medium QQ130 may be used to store computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions executable by the processing circuit QQ120. The device-readable medium QQ130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that may be used by the processing circuit QQ120. In some embodiments, the processing circuit QQ120 and the device-readable medium QQ130 may be considered integrated.
[0136] The user interface device QQ132 may provide a component that allows a human user to interact with the WD QQ110. This interaction may have a variety of forms, such as visual, auditory, tactile, etc. The user interface device QQ132 may be used to generate output to the user and allow the user to provide input to the WD QQ110. The type of interaction may vary, depending on the type of user interface device QQ132 installed in the WD QQ110. For example, if the WD QQ110 is a smart phone, 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 audible alarm (e.g., if smoke is detected). The user interface device QQ132 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device QQ132 is configured to allow information to be input to the WD QQ110, and is connected to the processing circuit QQ120 to allow the processing circuit QQ120 to process the input information. The user interface device QQ132 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device QQ132 is also configured to allow information to be output from the WD QQ110 and to allow the processing circuit 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 circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device QQ132, the WD QQ110 may communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.
[0137] The auxiliary device QQ134 is operable to provide more specific functions that the WD may not normally perform. This may include specialized sensors for measuring for various purposes, interfaces for additional communication types such as wired communications, etc. The contents and types of components of the auxiliary device QQ134 may vary depending on the embodiment and / or scenario.
[0138] In some embodiments, the power source QQ136 may 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., a power outlet), a photovoltaic device, or a battery. WD QQ110 may also include a power circuit QQ137 for transmitting power from the power source QQ136 to various parts of the WD QQ110 that require power from the power source QQ136 to perform any functions described or indicated herein. In some embodiments, the power circuit QQ137 may include a power management circuit. Additionally or alternatively, the power circuit QQ137 may be operable to receive power from an external power source; in this case, the WD QQ110 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a power cable). In some embodiments, the power circuit QQ137 may also be operable to transfer power from an external power source to the power source QQ136. This may be used, for example, to charge the power source QQ136. The power circuit QQ137 may perform any formatting, conversion, or other modification of the power from the power source QQ136 to make the power suitable for the corresponding components of the WD QQ110 that are powered thereon.
[0139] Fig.12 An embodiment of a UE according to various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user in terms of a human user who owns and / or operates the associated equipment. Conversely, a UE may represent a device that is intended to be sold to or operated by a human user, but may not be, or may not initially be, associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart meter). UEQQ200 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Fig.12 As shown, UE QQ200 is an example of a WD configured to communicate according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE and / or 5G standards. As mentioned above, the terms WD and UE can be used interchangeably. Therefore, although Fig.12 It is UE, but the components discussed in this article are also applicable to WD and vice versa.
[0140] exist Fig.12In the embodiment, UE QQ200 includes a processing circuit QQ201, which is operably coupled to an input / output interface QQ205, a radio frequency (RF) interface QQ209, 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 QQ221, 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 QQ225, and data QQ227. In other embodiments, the storage medium QQ221 may include other similar types of information. Some UEs may utilize Fig.12 All components shown, or only a subset of these components. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0141] exist Fig.12 In the embodiment of the present invention, the processing circuit QQ201 can be configured to process computer instructions and data. The processing circuit QQ201 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in a memory, such as one or more hardware-implemented state machines (e.g., in the form of discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination of the above. For example, the processing circuit QQ201 can include two central processing units (CPUs). The data can be information in a form suitable for use by a computer.
[0142] In the depicted embodiment, the input / output interface QQ205 may be configured to provide a communication interface to an input device, an output device, or an input and output device. 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 or 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, a transmitter, a smart card, another output device, or any combination thereof. The UE QQ200 may be configured to use an input device via the input / output interface QQ205 to allow the user to capture information into the UE QQ200. The input device may include a touch-sensitive display or a 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 steering wheel, a trackpad, a roller, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
[0143] exist Fig.12 In the embodiment of the present invention, the RF interface QQ209 can be configured to provide a communication interface to RF components such as transmitters, receivers and antennas. The network connection interface QQ211 can be configured to provide a communication interface to the network QQ243a. The network QQ243a can cover a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network QQ243a can include a Wi-Fi network. The network connection interface QQ211 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface QQ211 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or can be implemented separately.
[0144] RAM QQ217 can be configured to interface with processing circuit QQ201 via bus QQ202 to provide storage or buffering of data or computer instructions during execution of software programs such as operating systems, applications 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 unchanged low-level system code or data for basic system functions (e.g., basic input and output (I / O), startup, or keystrokes received from a keyboard) stored in non-volatile memory. Storage medium QQ221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette or flash drive. In one example, storage medium QQ221 can be configured to include operating system QQ223, application QQ225 such as a web browser application, widget or gadget engine or another application, and data file QQ227. The storage medium QQ221 may store any one of various operating systems or a combination of operating systems for use by the UE QQ200 .
[0145] The storage medium QQ221 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a user identity module (SIM) or a removable user identity (RUIM) module), other memory, or any combination thereof. The storage medium QQ221 may allow the UE QQ200 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article (such as an article utilizing a communication system) may be tangibly embodied in the storage medium QQ221, which may include a device-readable medium.
[0146] exist Fig.12In the embodiment of the present invention, the processing circuit QQ201 can be configured to communicate with the network QQ243b using the communication subsystem QQ231. The network QQ243a and the network QQ243b can be the same network or different networks. The communication subsystem QQ231 can be configured to include one or more transceivers for communicating with the network QQ243b. For example, the communication subsystem QQ231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (e.g., another WD, UE or base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.7, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include a transmitter QQ233 and / or a receiver QQ235 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter QQ233 and the receiver QQ235 of each transceiver can share circuit components, software or firmware, or can alternatively be implemented separately.
[0147] 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 using a global positioning system (GPS) to determine the location), another similar communication function, 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 a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network QQ243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE QQ200.
[0148] The features, benefits and / or functions described herein may be implemented in one of the components of UE QQ200, or may be divided between multiple components of UE QQ200. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem QQ231 may be configured to include any component described herein. In addition, the processing circuit QQ201 may be configured to communicate with any such component via bus QQ202. In another example, any such component may be represented by a program instruction stored in a memory, which executes the corresponding function described herein when executed by the processing circuit QQ201. In another example, the function of any such component may be divided between the processing circuit QQ201 and the communication subsystem QQ231. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.
[0149] Fig.13 is a schematic block diagram showing a virtualization environment QQ300 in which functions implemented by some embodiments can be virtualized. In the current context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and involves an implementation in which at least a portion of the functions are implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).
[0150] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more hardware nodes QQ330. Further, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.
[0151] These functions may be implemented by one or more applications QQ320 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.) to implement certain features, functions, and / or benefits of some embodiments disclosed herein. Applications QQ320 run in a virtualized environment QQ300, which provides hardware QQ330 including processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360, whereby applications QQ320 are operable to provide one or more features, benefits, and / or functions disclosed herein.
[0152] The virtualized environment QQ300 includes a general-purpose or special-purpose network hardware device QQ330, which includes a set of one or more processors or processing circuits QQ360, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), 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, which may be a non-persistent memory for temporarily storing instructions QQ395 or software executed by the processing circuit QQ360. Each hardware device may include one or more network interface controllers (NICs) QQ370 (also known as network interface cards), which include a physical network interface QQ380. Each hardware device may also include a non-temporary persistent machine-readable storage medium QQ390-2 in which software QQ395 and / or instructions executable by the processing circuit QQ360 are stored. Software QQ395 may include any type of software, including software for instantiating one or more virtualization layers QQ350 (also known as hypervisors), software for executing virtual machines QQ340, and software that enables them to perform functions, features and / or benefits associated with some of the embodiments described herein.
[0153] Virtual machine QQ340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of instances of virtual device QQ320 may be implemented on one or more virtual machines QQ340 and may be implemented in different ways.
[0154] During operation, processing circuit QQ360 executes software QQ395 to instantiate a hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present to virtual machine QQ340 a virtual operating platform that appears to be networked hardware.
[0155] like Fig.13As shown, hardware QQ330 can be an independent network node with common or specific components. Hardware QQ330 can include antenna QQ3225, and some functions can be implemented by virtualization. Alternatively, hardware QQ330 can be part of a larger hardware cluster (e.g., such as in a data center or customer premise equipment (CPE)), in which many hardware nodes work together and are managed by management and orchestration (MANO) QQ310 that oversees the life cycle management of application QQ320.
[0156] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises devices.
[0157] In the context of NFV, a virtual machine QQ 340 may be a software implementation of a physical program that runs the program as if it were executed on a physical, non-virtualized machine. Each virtual machine QQ 340 and the portion of the hardware QQ 330 on which it executes (whether hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines QQ 340) form a separate virtual network element (VNE).
[0158] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines QQ340 on top of the hardware network infrastructure QQ330 and interacting with Fig.13 Corresponding to the application QQ320.
[0159] In some embodiments, one or more radio units QQ3200 each include one or more transmitters QQ3220 and one or more receivers QQ3210, and 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 appropriate network interfaces, and may be used in conjunction with virtual components to provide radio capabilities to a virtual node, such as a radio access node or base station.
[0160] In some embodiments, some signaling may be accomplished using a control system QQ3230 , which may alternatively be used for communications between the hardware node QQ330 and the radio unit QQ3200 .
[0161] Fig.14 A telecommunications network connected to a host computer via an intermediate network is shown according to some embodiments. Fig.14According to an embodiment, a communication system includes a telecommunication network QQ410 such as a 3GPP type cellular network, which 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 Node Bs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c may be connected to the core network QQ414 via 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 in the coverage area QQ413a may be wirelessly connected to the corresponding base station QQ412a. Although multiple UEs QQ491 , QQ492 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or only one UE is connected to the corresponding base station QQ412 .
[0162] The telecommunications network QQ410 itself is connected to a host computer QQ430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer QQ430 may be under the ownership or control of a service provider, or may be operated by or on behalf of the 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 made through an optional intermediate network QQ420. The intermediate network QQ420 may be one of a public, private, or managed network, or a combination of multiple thereof; the intermediate network QQ420 (if any) may be a backbone network or the Internet; in particular, the intermediate network QQ420 may include two or more sub-networks (not shown).
[0163] Overall, Fig.14The communication system implements a connection between the connected UE QQ491, QQ492 and the host computer QQ430. The connection can be described as an Over-the-Top (OTT) connection QQ450. The host computer QQ430 and the connected computer UE QQ491, QQ492 are configured to use the access network QQ411, the core network QQ414, any intermediate network QQ420 and possible other infrastructure (not shown) as intermediaries to pass data and / or signaling via the OTT connection QQ450. The OTT connection QQ450 can be transparent in the sense that the participating communication devices through which the OTT connection QQ450 passes do not know the routes of the uplink and downlink communications. For example, the past route of the incoming downlink communication, which has data that originates from the host computer QQ430 and will be forwarded (e.g., handed over) to the connected UE QQ491, may not be notified or need not be notified to the base station QQ412. Similarly, base station QQ412 need not be aware of the future routing of outgoing uplink communications originating from UEQQ491 toward host computer QQ430.
[0164] According to one embodiment, reference will now be made to Fig.15 Example implementations of the UE, base station, and host computer discussed in the previous paragraphs are described. Fig.15 It is shown that the host computer according to some embodiments communicates with the user equipment via a base station through a partial wireless connection. In the communication system QQ500, the host computer QQ510 includes hardware QQ515, which includes a communication interface QQ516 configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system QQ500. The host computer QQ510 also includes a processing circuit QQ518, which can have storage and / or processing capabilities. In particular, the processing circuit QQ518 can include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer QQ510 also includes software QQ511, which is stored in the host computer QQ510 or can be accessed by the host computer QQ510 and can be executed by the processing circuit QQ518. The software QQ511 includes a host application QQ512. The host application QQ512 is operable to provide services to a remote user, such as a UE QQ530 connected via an OTT connection QQ50 terminating at the UE QQ530 and the host computer QQ510. In providing services to the remote user, the host application QQ512 may provide user data sent using the OTT connection QQ50.
[0165] The communication system QQ500 also includes a base station QQ520, which is provided in the telecommunication system and includes hardware QQ525 enabling it to communicate with the host computer QQ510 and with the UE QQ530. The hardware QQ525 may include a communication interface QQ526 for establishing and maintaining a wired or wireless connection with the different communication devices of the communication system QQ500, and a communication interface QQ526 for establishing and maintaining a connection with the network devices located in the coverage area ( Fig.15 The communication interface QQ526 may be configured to facilitate a connection QQ560 with the host computer QQ510. The connection QQ560 may be direct or may be through a core network (e.g., a wireless communication network) of the telecommunications system. Fig.15 ) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware QQ525 of the base station QQ520 also includes processing circuitry QQ528, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The base station QQ520 also has software QQ521 stored internally or accessible via an external connection.
[0166] The communication system QQ500 also includes the UE QQ530 already mentioned. Its hardware QQ535 may include a radio interface QQ537, which is configured to establish and maintain a wireless connection QQ570 with a base station serving the coverage area where the UE QQ530 is currently located. The hardware QQ535 of the UE QQ530 also includes a processing circuit QQ538, which may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE QQ530 further includes software QQ531 stored in the UE QQ530 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 is 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 executing host application QQ512 can communicate with the executing client application QQ532 through the OTT connection QQ550 terminated at the UE QQ530 and the host computer QQ510. In providing services to users, the client application QQ532 can receive request data from the host application QQ512 and provide user data in response to the request data. The OTT connection QQ550 can transmit both the request data and the user data. The client application QQ532 can interact with the user to generate the user data it provides.
[0167] Notice, Fig.15 The host computer QQ510, base station QQ520 and UE QQ530 shown can be respectively Fig.14 The host computer QQ430, one of the base stations QQ412a, QQ412b, QQ412c and one of the UEs QQ491, QQ492 are similar or identical. That is, the internal working principles of these entities can be as follows Fig.15 As shown, independently, the surrounding network topology can be Fig.14 Like that.
[0168] exist Fig.15 , an OTT connection QQ550 has been abstractly drawn to illustrate communications between a host computer QQ510 and a UE QQ530 via a base station QQ520, without explicit reference to any intermediate devices and the precise routing of messages via those devices. The network infrastructure may determine the routing and may be configured to hide the routing from the UE QQ530 or from the service provider operating the host computer QQ510, or both. When the OTT connection QQ550 is active, the network infrastructure may further make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).
[0169] The wireless connection QQ570 between the UE QQ530 and the base station QQ520 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improves the performance of OTT services provided to the UE QQ530 using the OTT connection QQ550, in which the wireless connection QQ570 forms the last segment.
[0170] The measurement process may be provided for the purpose of monitoring data rate, delay, and other factors that one or more embodiments improve. There may further be an optional network function for reconfiguring the OTT connection QQ550 between the host computer QQ510 and the UE QQ530 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection QQ550 may be implemented in the software QQ511 and hardware QQ515 of the host computer QQ510 or in the software QQ531 and hardware QQ535 of the UE QQ530 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection QQ550 passes. The sensor may participate in the measurement process by providing the value of the monitored quantity of the above example or providing the value of other physical quantities from which the software QQ511, QQ531 can calculate or estimate the monitored quantity. The reconfiguration of the OTT connection QQ550 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration does not have to affect the base station QQ520, and it may be unknown or imperceptible to the base station QQ520. Such processes and functions are known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer QQ510 to measure throughput, propagation time, latency, etc. The measurements may be implemented so that the OTT connection QQ550 is prompted to send messages, particularly empty or "dummy" messages, while software QQ511 and QQ531 monitor propagation time, errors, etc.
[0171] Fig.16 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.14 and 15 For the sake of simplicity of this disclosure, this section only includes Fig.16 Reference is made to the accompanying drawings of . In step QQ610, the host computer provides user data. In sub-step QQ611 of step QQ610 (which may be optional), the host computer provides user data by executing a host application. In step QQ620, the host computer initiates a transmission to the UE carrying the user data. In step QQ630 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
[0172] Fig.17 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.14 and 15 For the sake of simplicity of this disclosure, this section only includes Fig.17 . In step QQ710, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step QQ720, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout this disclosure, the transmission can be delivered via a base station. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
[0173] Fig.18 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.14 and 15 For the sake of simplicity of this disclosure, this section only includes Fig.18 . 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 of step QQ820 (which may be optional), the UE provides user data by executing a client application. In sub-step 811 of step QQ810 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, in sub-step QQ830 (which may be optional), the UE initiates transmission of user data to the host computer. In step QQ840 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.
[0174] Fig.19 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.14 and 15 For the sake of simplicity of this disclosure, only the Fig.19 In step QQ910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In step QQ920 (which may be optional), the base station initiates transmission of 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 initiated by the base station.
[0175] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via processing circuits that may include one or more microprocessors or microcontrollers and other digital hardware that may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical memory, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some implementations, according to one or more embodiments of the present disclosure, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding function.
[0176] Generally, unless different meanings are clearly given and / or implied in the context of using the term, all terms used in this article will be interpreted according to their common meaning in the relevant technical field. Unless clearly stated, all references to one / an / the element, equipment, assembly, device, step, etc. should be openly interpreted as referring to at least one instance of the element, equipment, assembly, device, step, etc. Unless a step must be clearly described as after or before another step and / or a step must be after or before another step implicitly, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applicable to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.
[0177] The term "unit" may have a conventional meaning in the field of electronic devices, electrical equipment and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, output and / or display functions, etc., such as those described herein.
[0178] Some embodiments contemplated herein are described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art.
[0179] Example
[0180] Group A Embodiment
[0181] A1. A method performed by a network device configured to implement a user plane function UPF, the UPF processing a user plane path of a protocol data unit PDU session between a wireless device and a data network DN, the method comprising:
[0182] receiving, from a first session management function SMF configured to manage the PDU session, a request to release a signaling session established between the UPF and the first SMF for the PDU session; and
[0183] Receive control signaling from the first SMF indicating that the signaling session with the UPF will be re-established.
[0184] A2. A method according to embodiment A1, wherein the control signaling indicates that the second SMF will re-establish a signaling session with the UPF.
[0185] A3. A method according to embodiment A1, wherein the control signaling indicates that the first SMF will re-establish a signaling session with the UPF.
[0186] A4. The method according to any one of embodiments A1-A3, further comprising:
[0187] storing, at the UPF, a context for the signalling session prior to receiving the request; and
[0188] Based on control signaling, information from the context is retained regardless of a request to release the signaling session.
[0189] A5. The method of embodiment A4, wherein the retained information includes one or more of the following:
[0190] The Internet Protocol (IP) address for the PDU session on the interface between the UPF and the DN;
[0191] a device identifier that identifies the wireless device;
[0192] a session identifier identifying the signalling session; or
[0193] Information identifying a tunnel used for a PDU session, where the tunnel is a radio-side tunnel between a UPF and a radio network node or a DN-side tunnel between a UPF and a DN.
[0194] A6. A method according to any one of embodiments A4-A5, wherein the retaining includes: storing information from the context until the signaling session is re-established.
[0195] A7. The method according to any one of embodiments A2-A5, further comprising:
[0196] After receiving the request, receiving the packet at the UPF; and
[0197] The packet is processed using the retained information from the context for the signaling session.
[0198] A8. A method according to embodiment A7, wherein the processing includes: forwarding packets or buffering packets.
[0199] A9. A method according to any one of embodiments A7-A8, wherein the retained information from the context includes information identifying a tunnel used for the PDU session, and wherein the processing includes forwarding packets in the tunnel, wherein the tunnel is a radio side tunnel between the UPF and the radio network node or a DN side tunnel between the UPF and the DN.
[0200] A10. A method according to any one of embodiments A7-A9, wherein the processing includes: buffering packets until the signaling session is re-established.
[0201] A11. The method according to any one of embodiments A2-A10 further includes: re-establishing a signaling session.
[0202] A12. The method of embodiment A11, wherein the re-establishing comprises: using the retained information from the context to re-establish the signaling session.
[0203] A13. A method according to any one of embodiments A1-A12, wherein the re-established signaling session is identified by the same session identifier as the signaling session established between the UPF and the first SMF, and / or is associated with the same PDU session IP address on the interface between the UPF and the DN.
[0204] A14. The method of any one of embodiments A1-A13, wherein control signaling is included in the request.
[0205] A15. A method according to any one of embodiments A1-A13, wherein the control signaling is included in a request to update or modify the signaling session from the first SMF.
[0206] A16. A method according to any one of embodiments A1-A15, wherein the control signaling includes information elements in a Packet Forwarding Control Protocol PFCP communication from the first SMF.
[0207] A17. A method according to any one of embodiments 1A-A16, wherein the control signaling is included in a general tunneling protocol GTP user plane extension header of a packet forwarding control protocol PFCP tunnel established between the first SMF and the UPF.
[0208] A18. A method according to any one of embodiments A1-A17, wherein the control signaling includes a flag whose presence indicates that the signaling session is to be re-established.
[0209] Group B Example
[0210] B1. A method performed by a network device configured to implement a first session management function SMF, the first SMF managing a protocol data unit PDU session between a wireless device and a data network DN, the method comprising:
[0211] Sending a request to release a signaling session from the first SMF to a user plane function UPF that handles a user plane path of the PDU session, the signaling session being established between the UPF and the first SMF for the PDU session; and
[0212] Control signaling is sent from the first SMF to the UPF indicating that the signaling session is to be re-established.
[0213] B2. The method according to embodiment B1 further includes: receiving a transfer request requesting the first SMF to transfer the session management context at the first SMF for the PDU session to the second SMF, and wherein control signaling is sent based on the reception of the transfer request.
[0214] B3. The method of embodiment B1, further comprising: determining that the wireless device is operating in a sleep state, and wherein control signaling is sent based on the determination.
[0215] B4. A method according to any one of embodiments B1-B3, wherein the signaling session to be re-established is identified by the same session identifier as the signaling session established between the UPF and the first SMF, and / or is associated with the same PDU session IP address on the interface between the UPF and the DN.
[0216] B5. The method of any one of embodiments B1-B4, wherein control signaling is included in the request.
[0217] B6. A method according to any one of embodiments B1-B4, wherein the control signaling is included in a request to update or modify the signaling session from the first SMF.
[0218] B7. A method according to any one of embodiments B1-B6, wherein the control signaling includes information elements in a Packet Forwarding Control Protocol PFCP communication from the first SMF.
[0219] B8. A method according to any one of embodiments B1-B7, wherein the control signaling is included in a general tunneling protocol GTP user plane extension header of a packet forwarding control protocol PFCP tunnel established between the first SMF and the UPF.
[0220] B9. A method according to any one of embodiments B1-B8, wherein the control signaling includes a flag whose presence indicates that the signaling session is to be re-established.
[0221] Group C Example
[0222] C1. A network device configured to perform any steps of any one of Group A or Group B embodiments.
[0223] C2. A network device comprising a processing circuit configured to perform any steps of any of Group A or Group B embodiments.
[0224] C3. A network device comprising:
[0225] communications circuits; and
[0226] A processing circuit configured to perform any step of any of the Group A or Group B embodiments.
[0227] C4. A network device comprising:
[0228] A processing circuit configured to perform any of the steps of any of Group A or Group B embodiments; and
[0229] A power circuit is configured to supply power to the network device.
[0230] C5. A network device comprising:
[0231] A processing circuit and a memory, the memory containing instructions executable by the processing circuit, whereby the network device is configured to perform any steps of any of the Group A or Group B embodiments.
[0232] C6. A computer program comprising instructions which, when executed by at least one processor of a network device, cause the network device to perform the steps of any one of Group A or Group B embodiments.
[0233] C7. A carrier containing the computer program of embodiment C6, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.
[0234] abbreviation
[0235] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between the abbreviations, the above usage should be preferred. If listed multiple times below, the first listing should take precedence over subsequent listings.
[0236] 5GC Fifth Generation Core Network
[0237] AMF Access and Mobility Management Function
[0238] DN Data Network
[0239] NF Network Function
[0240] PDU Packet Data Unit
[0241] SBA Service-Based Architecture
[0242] SMF session management functions
[0243] UE User Equipment
[0244] UP User Plane
[0245] UPF User Plane Function
[0246] 1x RTT CDMA2000 1x Radio Transmission Technology
[0247] 3GPP Third Generation Partnership Project
[0248] 5G Fifth Generation
[0249] ABS Almost Blank Subframe
[0250] ARQ Automatic Repeat Request
[0251] AWGN Additive White Gaussian Noise
[0252] BCCH Broadcast Control Channel
[0253] BCH Broadcast Channel
[0254] CA Carrier Aggregation
[0255] CC Carrier Component
[0256] CCCH SDU Common Control Channel SDU
[0257] CDMA Code Division Multiplexing
[0258] CGI Cell Global Identifier
[0259] CIR Channel Impulse Response
[0260] CP Cyclic Prefix
[0261] CPICH Common Pilot Channel
[0262] CPICH Ec / No The CPICH received energy per chip is divided by the power density in the frequency band
[0263] CQI Channel Quality Information
[0264] C-RNTI Cell RNTI
[0265] CSI Channel State Information
[0266] DCCH Dedicated Control Channel
[0267] DL Downlink
[0268] DM Demodulation
[0269] DMRS Demodulation Reference Signal
[0270] DRX Discontinuous Reception
[0271] DTX Discontinuous Transmission
[0272] DTCH Dedicated Traffic Channel
[0273] DUT Device Under Test
[0274] E-CID Enhanced Cell ID (positioning method)
[0275] E-SMLC Evolved Service Mobile Location Center
[0276] ECGI Evolution CGI
[0277] eNB E-UTRAN Node B
[0278] ePDCCH Enhanced Physical Downlink Control Channel
[0279] E-SMLC Evolved Service Mobile Location Center
[0280] E-UTRA Evolved UTRA
[0281] E-UTRAN Evolved UTRAN
[0282] FDD Frequency Division Duplex
[0283] FFS needs further study
[0284] GERAN GSM EDGE Radio Access Network
[0285] Base stations in gNB NR
[0286] GNSS Global Navigation Satellite System
[0287] GSM Global System for Mobile Communications
[0288] HARQ Hybrid Automatic Repeat Request
[0289] HO Handover
[0290] HSPA High Speed Packet Access
[0291] HRPD High Rate Packet Data
[0292] LOS Line of Sight
[0293] LPP LTE Positioning Protocol
[0294] LTE Long Term Evolution
[0295] MAC Media Access Control
[0296] MBMS Multimedia Broadcast Multicast Service
[0297] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
[0298] MBSFN ABS MBSFN Almost Blank Subframe
[0299] MDT Minimized Drive Test
[0300] MIB Master Information Block
[0301] MME Mobility Management Entity
[0302] MSC Mobile Switching Center
[0303] NPDCCH Narrowband Physical Downlink Control Channel
[0304] NR New Radio
[0305] OCNG OFDMA Channel Noise Generator
[0306] OFDM Orthogonal Frequency Division Multiplexing
[0307] OFDMA Orthogonal Frequency Division Multiple Access
[0308] OSS Operation Support System
[0309] OTDOA Observed Time Difference of Arrival
[0310] O&M Operation and Maintenance
[0311] PBCH Physical Broadcast Channel
[0312] P-CCPCH Primary Common Control Physical Channel
[0313] PCell Primary Cell
[0314] PCFICH Physical Control Format Indicator Channel
[0315] PDCCH Physical Downlink Control Channel
[0316] PDP Power Delay Profile
[0317] PDSCH Physical Downlink Shared Channel
[0318] PGW Packet Gateway
[0319] PHICH Physical Hybrid ARQ Indicator Channel
[0320] PLMN Public Land Mobile Network
[0321] PMI precoder matrix indication
[0322] PRACH Physical Random Access Channel
[0323] PRS Positioning Reference Signal
[0324] PSS Primary Synchronization Signal
[0325] PUCCH Physical Uplink Control Channel
[0326] PUSCH Physical Uplink Shared Channel
[0327] RACH Random Access Channel
[0328] QAM Quadrature Amplitude Modulation
[0329] RAN Radio Access Network
[0330] RAT Radio Access Technology
[0331] RLM Radio Link Management
[0332] RNC Radio Network Controller
[0333] RNTI Radio Network Temporary Identifier
[0334] RRC Radio Resource Control
[0335] RRM Radio Resource Management
[0336] RS reference signal
[0337] RSCP Received Signal Code Power
[0338] RSRP Reference Symbol Received Power or Reference Signal Received Power
[0339] RSRQ Reference Signal Received Quality or Reference Symbol Received Quality
[0340] RSSI Received Signal Strength Indicator
[0341] RSTD Reference Signal Time Difference
[0342] SCH Synchronization Channel
[0343] SCell Secondary Cell
[0344] SDU Service Data Unit
[0345] SFN System Frame Number
[0346] SGW Service Gateway
[0347] SI System Information
[0348] SIB System Information Block
[0349] SNR Signal to Noise Ratio
[0350] SON Self-Optimizing Network
[0351] SS Sync Signal
[0352] SSS Secondary synchronization signal
[0353] TDD Time Division Duplex
[0354] TDOA Time Difference of Arrival
[0355] TOA Time of Arrival
[0356] TSS three-level synchronization signal
[0357] TTI Transmission Time Interval
[0358] UE User Equipment
[0359] UL Uplink
[0360] UMTS Universal Mobile Telecommunications System
[0361] USIM Universal Subscriber Identity Module
[0362] UTDOA Uplink Time Difference of Arrival
[0363] UTRA Universal Terrestrial Radio Access
[0364] UTRAN Universal Terrestrial Radio Access Network
[0365] WCDMA Wideband CDMA
[0366] WLAN Wide Area Network
Claims
1. A method performed by a network device configured to implement a user plane function UPF, wherein the UPF processes a user plane path of a protocol data unit PDU session between a wireless device and a data network DN, wherein the method include: Receiving, from a first session management function SMF configured to manage the PDU session, an N4 session release request for releasing an N4 session between the UPF and the first SMF for the PDU session, the N4 session release request including a flag indicating that the N4 session for the PDU session will be reestablished with the UPF; Based on the flag, delaying the release of the N4 session; as well as A request to reestablish the N4 session for the PDU session is received from the first SMF or another SMF.
2. The method according to claim 1, in, The flag indicates that the second SMF will re-establish the N4 session with the UPF.
3. The method according to claim 1, in, The flag indicates that the first SMF will re-establish the N4 session with the UPF.
4. The method according to claim 1, in, The delay includes delaying the release of the N4 session at least until the re-establishment of the N4 session.
5. The method according to claim 1, further comprising: include: After receiving the N4 session release request, the context for the N4 session is stored at the UPF, at least until the N4 session is re-established.
6. The method according to claim 1, further comprising: include: When receiving the N4 session release request, storing a context for the N4 session at the UPF; as well as Packets received for the PDU session after receiving the N4 session release request are processed using information from the stored context for the N4 session.
7. The method according to claim 6, in, The information used includes information identifying a tunnel used for the PDU session, and wherein the processing includes forwarding the packet in the tunnel, wherein the tunnel is a radio side tunnel between the UPF and a radio network node or a DN side tunnel between the UPF and the DN.
8. The method according to claim 1, further comprising: include: The N4 session is reestablished, wherein the reestablishing comprises: using information from the stored context to reestablish the N4 session.
9. The method according to claim 1, in, The N4 session to be re-established is identified by the same session identifier as the N4 session established between the UPF and the first SMF, and / or the N4 session to be re-established is associated with the same PDU session IP address on the interface between the UPF and the DN.
10. A method performed by a network device configured to implement a first session management function SMF, wherein the first SMF manages a protocol data unit (PDU) session between a wireless device and a data network DN, wherein the method include: An N4 session release request for releasing the N4 session between the UPF and the first SMF for the PDU session is sent from the first SMF to the user plane function UPF that handles the user plane path of the PDU session, and the N4 session release request includes a flag indicating that the N4 session for the PDU session will be re-established with the UPF and that the UPF should delay the release of the N4 session.
11. The method according to claim 10, further comprising: include: A transfer request is received requesting the first SMF to transfer a session management context for the PDU session at the first SMF to a second SMF, and wherein the flag is sent based on the receipt of the transfer request.
12. The method according to claim 10, further comprising: include: A determination is made that the wireless device is operating in a sleep state, and wherein the flag is sent based on the determination.
13. The method according to claim 10, in, The N4 session to be re-established is identified by the same session identifier as the N4 session established between the UPF and the first SMF, and / or the N4 session to be re-established is associated with the same PDU session IP address on the interface between the UPF and the DN.
14. A network device configured to implement a user plane function UPF for processing a user plane path of a protocol data unit PDU session between a wireless device and a data network DN, the network device include: Communication circuits; as well as A processing circuit configured to: Receiving, from a first session management function SMF configured to manage the PDU session, an N4 session release request for releasing an N4 session between the UPF and the first SMF for the PDU session, the N4 session release request including a flag indicating that the N4 session for the PDU session will be reestablished with the UPF; Based on the flag, delaying the release of the N4 session; as well as A request to reestablish the N4 session for the PDU session is received from the first SMF or another SMF.
15. The network device according to claim 14, in, The flag indicates that the second SMF will re-establish the N4 session with the UPF.
16. The network device according to claim 14, in, The flag indicates that the first SMF will re-establish the N4 session with the UPF.
17. The network device according to claim 14, in, The processing circuit is configured to delay the release of the N4 session at least until the re-establishment of the N4 session.
18. The network device according to claim 14, in, The processing circuit is further configured to: after receiving the N4 session release request, store the context for the N4 session at the UPF, at least until the N4 session is re-established.
19. The network device according to claim 14, in, The processing circuit is further configured to: When receiving the N4 session release request, storing a context for the N4 session at the UPF; as well as Packets received for the PDU session after receiving the N4 session release request are processed using information from the stored context for the N4 session.
20. The network device according to claim 19, in, The information used includes information identifying a tunnel used for the PDU session, and wherein the processing circuit is configured to forward the packet in the tunnel, wherein the tunnel is a radio side tunnel between the UPF and a radio network node or a DN side tunnel between the UPF and the DN.
21. The network device according to claim 14, in, The processing circuit is further configured to reestablish the N4 session using information from the stored context.
22. The network device according to claim 14, in, The N4 session to be re-established is identified by the same session identifier as the N4 session established between the UPF and the first SMF, and / or the N4 session to be re-established is associated with the same PDU session IP address on the interface between the UPF and the DN.
23. A network device configured to implement a first session management function SMF for managing a protocol data unit (PDU) session between a wireless device and a data network DN, wherein the network device include: Communication circuits; as well as A processing circuit is configured to: send an N4 session release request from the first SMF to a user plane function UPF that handles the user plane path of the PDU session to release the N4 session between the UPF and the first SMF for the PDU session, wherein the N4 session release request includes a flag indicating that the N4 session for the PDU session will be re-established with the UPF and that the UPF should delay the release of the N4 session.
24. The network device according to claim 23, in, The processing circuit is further configured to receive a transfer request requesting the first SMF to transfer a session management context for the PDU session at the first SMF to a second SMF, and wherein the processing circuit is configured to send the flag based on receipt of the transfer request.
25. The network device according to claim 23, in, The processing circuit is further configured to determine that the wireless device is operating in a sleep state, and wherein the processing circuit is configured to send the flag based on the determination.
26. The network device according to claim 23, in, The N4 session to be re-established is identified by the same session identifier as the N4 session established between the UPF and the first SMF, and / or the N4 session to be re-established is associated with the same PDU session IP address on the interface between the UPF and the DN.
