CN113366884B

CN113366884B - User data interworking in wireless systems

Info

Publication number: CN113366884B
Application number: CN201880098185.0A
Authority: CN
Inventors: 朱进国
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-09-28
Filing date: 2018-09-28
Publication date: 2023-08-11
Anticipated expiration: 2038-09-28
Also published as: WO2020034334A1; CN113366884A

Abstract

A method, system and apparatus for user data interworking in a wireless system are described. The disclosed techniques advantageously enable a terminal to register in a single network among two or more available networks without adversely affecting legacy systems. An exemplary method for wireless communication includes: receiving, by a first network device associated with a first network, a first message, wherein the first message comprises a request for registration of a terminal in the first network, and the first network device sends a second message to a second network device associated with a second network, the second message comprising an identifier and an indication of the sending of subscription data bypassing the terminal in the second network.

Description

User data interworking in wireless systems

Technical Field

The document is generally directed to wireless communications and, in particular, to user data interworking in a wireless system.

Background

Wireless communication technology is evolving the world towards increasingly connected and networked society. The rapid growth of wireless communications and advances in technology have led to greater demands for capacity and connectivity. Other aspects, such as energy consumption, equipment cost, spectral efficiency and latency, are also important to meet the needs of various communication scenarios. Next generation systems and wireless communication technologies need to provide support for more and more users and devices and support for higher data rates than existing wireless networks, thereby requiring user devices to implement power saving techniques.

Disclosure of Invention

This document relates to methods, systems and devices for user data interworking in wireless systems, such as 4th Generation (4G) and 5th Generation (5G) cellular systems. Among other benefits, embodiments of the disclosed technology provide support for single registration of terminals without adversely affecting legacy systems.

In one exemplary aspect, a method of wireless communication is disclosed. The method comprises the following steps: receiving, by a first network device associated with a first network, a first message, wherein the first message comprises a request for registration of a terminal in the first network, and the first network device sends a second message to a second network device associated with a second network, the second message comprising an identifier and an indication of transmission of subscription data bypassing the terminal in the second network.

In yet another exemplary aspect, the above-described method is embodied in the form of processor-executable code and stored in a computer-readable program medium.

In yet another exemplary embodiment, an apparatus configured or operable to perform the above method is disclosed.

The above and other aspects and embodiments thereof are described in more detail in the accompanying drawings, the description and the claims.

Drawings

Fig. 1 illustrates an example of a Base Station (BS) and a User Equipment (UE) in wireless communication in accordance with some embodiments of the disclosed technology.

Fig. 2 shows an exemplary embodiment for supporting interworking between an Evolved Packet System (EPS) and a fifth generation system (5 GS).

Fig. 3 shows another exemplary embodiment for supporting interworking between EPS and 5 GS.

Fig. 4 shows an example timing flow diagram for registering a UE in a 5G system after the UE has registered in the 4G system.

Fig. 5 shows an example timing flow diagram for registering a UE in a 4G system after the UE has registered in the 5G system.

Fig. 6 shows an example timing flow diagram for de-registering a UE in a 5G system after the UE has registered in the 5G system.

Fig. 7 illustrates an example of a wireless communication method in accordance with some embodiments of the presently disclosed technology.

Fig. 8 is a block diagram representation of a portion of a device in accordance with some embodiments of the disclosed technology.

Detailed Description

Some existing implementations of 5th Generation (5G) networks include heterogeneous networks that combine different types of infrastructures and different standards, e.g., WLAN, WIMAX,3G,4G, that operate at different frequencies and have different architectures. Embodiments of heterogeneous architectures tend to enhance network coverage and capacity and improve spectral efficiency. However, integration of these architectures requires interworking functions to provide seamless coverage for the user.

In an example, the third generation mobile communication partner project (3 rd Generation partnership project, abbreviated 3 GPP) has a unified data architecture based on a unified data store (Unified Data Repositories, abbreviated UDR). To migrate between 4G and 5G, a node (referred to as a combined hss+udm node) that combines the functions of a local subscriber subsystem (Home Subscriber Subsystem, abbreviated HSS) and a unified data management (Unified Data Management, abbreviated UDM) system is introduced to support interworking between an evolved packet switching center (Evolved Packet Core, abbreviated EPC) and a 5G Core (5G Core, abbreviated 5 GC) network.

However, in some embodiments, the interface between the HSS and the evolved packet domain system (Evolved Packet System, simply EPS) EPS UDR has not been specified in 4G, which limits the deployment of 5GC, as operators have to deploy these combined nodes from the same vendor of HSS and EPS UDR. Embodiments of the disclosed technology define, among other features, a new interface between the HSS and the UDM in order to support flexible deployment of 5GS UDR and UDM. Furthermore, the disclosed technology supports single registration between 4G and 5G without any impact on legacy systems.

Fig. 1 shows an example of a wireless communication system (e.g., LTE,5G or New Radio, NR) cellular network) including a Base Station (BS) 120 and one or more User Equipments (UEs) 111, 112 and 113 in some embodiments, after registering with only the 5G network, the 5G BS (e.g., eNB, gNB) may communicate with the UEs (141, 142, 143) and vice versa (131, 132, 133).

This document uses section headings and sub-headings to facilitate ease of understanding, and does not limit the scope of the disclosed techniques and embodiments to certain sections. Thus, the embodiments disclosed in the different sections may be used with each other. Furthermore, this document uses only examples from the 3GPP New Radio (NR) network architecture and 5G protocols to facilitate understanding, and the disclosed techniques and embodiments may be practiced in other wireless systems using different communication protocols than the 3GPP protocols.

Exemplary architecture for user data interworking

Fig. 2 shows an exemplary embodiment for supporting interworking between EPS and 5th generation systems (5 th Generation System, simply 5 GS). As shown in the figure, the combined hss+udm node 215 is configured to support interworking between component systems. The HSS is a 4G function that supports 4G subscription processing. It uses the S6a interface and mobility management element (Mobility Management Element, abbreviated MME) 260. The HSS accesses the 4G subscription stored in the EPS UDR 230 through the Ud interface. The Ud interface is not specified and is vendor specific. Unified data management (Unified Data Management, abbreviated UDM) is a support for 5G subscription handling 5G functions. It uses a service-based interface Nudm with an access mobility function (Access Mobility Function, abbreviated as AMF) 250. The UDM accesses the 5gs UDR 240 via the Nudr interface. The Nudr interface is an interface based on standardized services. In some embodiments, the Ud interface is not specified, which requires that the 5GS UDR and the combined hss+udm should be deployed from the same vendor as the EPS UDR.

Fig. 3 shows another exemplary embodiment for supporting interworking between EPS and 5 GS. As shown, the Shu interface is introduced between HSS 310 and UDM 320. In order not to affect the legacy HSS, this interface is based on Diameter as S6a. When a 4G user is updated to a 5G user, the 4G subscription profile will be stored in EPS UDR 330 and new 5G subscription data will be provided in 5gs UDR 340. EPS UDR and 5GS UDR are typically from different vendors and deployed separately, meaning that there is no interface between EPS UDR and 5G UDR.

In some embodiments, UDM 320 is the first access point of 4G and 5G. UDM interfaces with AMF 350 using Nudm and interfaces with MME 260 using S6a MME. Thus from the MME point of view, the UDM is the HSS. Furthermore, the UDM relays messages between the HSS and the MME.

In some embodiments, the 5GS supports a single registration mode, where the UE registers only in 4G or 5G, but not in both. This means that when a UE registers in 4G, it should be separated in 5G and vice versa. Since there is no direct interface between EPS UDR and 5GS UDR, it is not clear in existing systems to support a single registration mode.

Embodiments of the disclosed technology advantageously achieve the following objectives:

(1) When the UDM receives a UE registration with a single registration indication from the AMF over 5G, it will generate an update location request with a dedicated MME identity to the HSS over Shu to perform 4G registration in EPS UDR.

(2) When the UE has registered in an old MME, the HSS will send a cancel location request to the old MME, which results in the UE being separated from the old MME.

(3) Later, when the UE registers with the new MME through 4G, the new MME sends an update location request to the UDM, which relays this message to the HSS. Then, the HSS sends the cancel location to the UDM, which then sends UE deregistration information to the AMF, thereby separating the UE from the AMF.

Example timing flow diagrams of the disclosed technology

Fig. 4 shows an example timing flow diagram for registering a UE in a 5G system after the UE has registered in the 4G system. As described below, messages are passed between the AMFs 450,MME 460,UDM 420, 5GS UDR 440,HSS 410 and the EPS UDR430, as shown in fig. 4.

1. In some embodiments, the AMF registers with the UDM using a Nudm_UECM_Registration request. In some embodiments, the message includes UE identity (SUPI, subscription permanent identifier), AMF information, and may also include whether a single registration or double registration is required.

UDM calls nudr_udm_update to store AMF information into UDR.

Udm sends nudm_uecm_registration response to AMF.

AMF sends a Nudm_SDM_get request to UDM to Get a subscription.

UDM invokes nudr_udm_query service to Query UE subscription from UDR.

Udm sends UE subscription by invoking nudm_sdm get response.

7. When the UE subscribes to change or the UDM deregisters the AMF, the AMF also sends a Nudm_SDM_Subscribion request to subscribe.

UDM invokes nudr_udm_subscore service to subscribe to UE subscriptions and any changes in UE context.

Udm sends nudm_sdm_description response to AMF.

Udm checks if a single registration is required. If not, the process stops, otherwise the following steps are performed.

The udm selects HSS based on the UE ID and sends an update location request to HSS. In this message, a dedicated MME identity is included. This dedicated MME identity points to UDM. From the perspective of the HSS, the UDM now acts as an MME. The message also includes an indication of a single registration and an indication to skip transmission of subscription data, so the HSS will not send UE 4G subscription data.

The hss stores the dedicated MME identity into the EPS UDR over the Ud interface.

The udm sends an update location response to the HSS.

14. If the UE has registered in a different MME, the HSS sends a cancel location request to the MME. The message will be routed directly to the MME based on the MME identity.

15. The new MME deregisters the UE and sends a cancel location response to the HSS.

Fig. 5 shows an example timing flow diagram for registering a UE in a 4G system after the UE has registered in the 5G system. As described below, as shown in fig. 5, messages are passed between the AMFs 550,MME 560,UDM 520, 5GS UDR 540,HSS 510 and the EPS UDR 530.

1. In some embodiments, since the UDM is the first access point of both 4G and 5G, the MME sends an update location request to the UDM. The message includes UE identity and MME information.

The udm forwards the update location request to the HSS.

And the HSS stores the MME information into the EPS UDR through the Ud interface.

The hss sends the update location response to the UDM comprising the UE 4G subscription.

Udm forwards the update location response to MME including UE 4G subscription.

6. If the UE is registered in 5G and the dedicated MME identity is stored in EPS UDR, EPS UDR triggers HSS to send cancel location request to UDM. The message will be routed to the UDM based on the dedicated MME identity.

The udm sends a cancel location response to the HSS.

8. Upon receiving a cancel location request from the HSS to deregister the UE in 5G, the UDM will invoke nudr_udm_update to delete the UE context stored in 5GS UDR.

Udm sends nudm_uecm_DeregiotionNotification to AMF (i.e. previously registered UE).

AMF separates UEs and then sends Nudm_UECM_ DeregistrationNotification ACK to UDM.

The amf also sends a nudm_sdm_un ubscript request to the UDM to Unsubscribe from the UE subscription change notification.

Udm sends nudm_sdm_un ubscript response to AMF.

Fig. 6 shows an example timing flow diagram for de-registering a UE in a 5G system after the UE has registered in the 5G system. As described below, messages are transferred between the AMFs 650,MME 660,UDM 620, 5GS UDR 640,HSS 610 and the EPS UDR 630, as shown in fig. 6.

1. In some embodiments, and after separating the UE into an AMF, the AMF sends a nudm_uecm_Deregistration request to the UDM.

UDM calls nudr_udm_update to delete AMF information stored in UDR.

Udm sends nudm_uecm_Deregistration response to AMF.

4. When the UE subscribes to a change or the UDM deregisters the AMF, the AMF also sends a Nudm_SDM_UnSubscribe request to cancel the subscription to be notified.

UDM invokes nudr_udm_un subscribe service to delete notifications about UE subscription and any changes to UE context.

Udm sends nudm_sdm_un description response to AMF.

The udm checks if it is registered in the HSS/EPS UDR and if so sends a clear UE request to the HSS.

Hss deletes the dedicated MME identity of UDM in EPS UDR.

The hss sends a clear UEA Ack to the UDM.

Exemplary methods for the disclosed technology

Embodiments of the disclosed technology may implement an exemplary method at a UDM for supporting user data interworking in a wireless system, the method comprising:

(1) Receiving a UE registration request from an AMF, wherein the message includes a single registration indication;

(2) Sending an update location request to the HSS, including an MME identity pointing to the UDM and an indication to skip subscription data;

(3) Receiving a cancel location request from the HSS;

(4) Updating the UDR to delete AMF information; and

(5) A UE de-registration request is sent to the AMF to de-register the UE in the AMF.

Fig. 7 illustrates an example of a wireless communication method 700 for user data interworking in a wireless system. The method 700 includes, at step 710, receiving a first message at a first network device associated with a first network, the first message including a request for registration of a terminal in the first network. In some embodiments, the request comprises a single registration request corresponding to registering the terminal in the first network but not the second network.

The method 700 includes, at step 720, transmitting, by the first network device, a second message to a second network device associated with the second network, the second message including an identifier and an indication of transmission of subscription data bypassing terminals in the second network. In some embodiments, the identifier is associated with the first network.

The method 700 further comprises the step of selecting the second network device based on the identity of the terminal. In an example, the UE identity is used by the UDM to select the HSS (e.g., step 11 in fig. 4).

The method 700 further comprises the steps of: a third message is received from the second network device, the third message including a request to log off the terminal from the first network. In an example, the UDM receives a cancel location request (Cancel Location Request, abbreviated CLR) from the HSS to de-register the UE in the 5G network (e.g., step 8 in fig. 5). In some embodiments, this may be followed by updating the repository by removing information corresponding to the terminal being registered in the first network.

In some embodiments, a first message is received from a third network device (e.g., step 1 in fig. 4, where a nudm_uecm_registration request including an indication indicating whether a single Registration is required or a double Registration is required is received from the AMF). The method 700 further includes sending a fourth message to a fourth network device, the fourth message including a request to log off the terminal from the first network. In an example, the UDM sends a nudm_sdm_un ubscript response to the AMF (e.g., step 12 in fig. 5).

In some embodiments, the first network device is a unified data management (Unified Data Management, abbreviated UDM) system, the second network device is a home subscriber subsystem (Home Subscriber Subsystem, abbreviated HSS), the identifier is a mobility management entity (Mobile Management Entity, abbreviated MME) identity, and the first and second networks are a fifth generation (5G) network and a fourth generation (4G) network, respectively.

Embodiments of the disclosed technology

Fig. 8 is a block diagram representation of a portion of a device in accordance with some embodiments of the disclosed technology. The device 805, such as a base station or a wireless device (or UE), may include a processor electronic device 810, such as a microprocessor, that implements one or more of the techniques presented in this document. Device 805 may include transceiver electronics 815 to transmit and/or receive wireless signals through one or more communication interfaces (e.g., antenna 820). The device 805 may include other communication interfaces for transmitting and receiving data. Device 805 may include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some implementations, the processor electronics 810 can include at least a portion of the transceiver electronics 815. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the device 805.

It is intended that the specification, together with the drawings, be considered exemplary only, with exemplary meaning given herein, and not intended to mean an ideal or preferred embodiment unless otherwise specified. As used herein, the use of "or" is intended to include "and/or" unless the context clearly indicates otherwise.

Some embodiments described herein are described in the general context of methods or processes, which may be implemented in one embodiment by a computer program product embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by computers in networked environments. The computer readable medium may include removable and non-removable storage devices including, but not limited to, read Only Memory (ROM), random access Memory (Random Access Memory RAM), compact Discs (CD), digital versatile discs (digital versatile discs DVD), and the like. Thus, the computer readable medium may include a non-transitory storage medium. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer or processor executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

Some of the disclosed embodiments may be implemented as a device or module using hardware circuitry, software, or a combination thereof. For example, a hardware circuit implementation may include discrete analog and/or digital components, for example, integrated as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASICs) and/or field programmable gate array (Field Programmable Gate Array, abbreviated as FPGAs) devices. Some embodiments may additionally or alternatively include a digital signal processor (digital signal processor, abbreviated DSP) that is a special purpose microprocessor having an architecture optimized for the operational requirements of digital signal processing associated with the disclosed functionality of the present application. Similarly, the various components or sub-components within each module may be implemented in software, hardware, or firmware. Any connection method and medium known in the art can be used to provide connectivity between modules and/or components within modules, including but not limited to the internet, communication over wired or wireless networks using appropriate protocol connections.

While this document contains many specifics, these should not be construed as limitations on the scope of the claimed application or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features that are described herein in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features can in some cases be excised from the claimed combination and the claimed combination may be directed to a subcombination or variation of a subcombination. Similarly, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results.

Only some embodiments and examples are described and other embodiments, enhancements and variations may be made based on what is described and shown in the present disclosure.

Claims

1.A method of wireless communication, comprising:

receiving, by a first network device associated with a first network, a first message, wherein the first message comprises a request for a terminal to register in the first network, wherein the request comprises a single registration request corresponding to registering the terminal in the first network but not in a second network; and

the first network device sends a second message to a second network device associated with a second network, wherein the second message comprises an identifier and an indication of the sending of subscription data bypassing terminals in the second network, wherein the first network device is a unified data management, UDM, system, wherein the second network device is a home subscriber subsystem, HSS, wherein the identifier is a mobile management entity, MME, identity, and wherein the first and second networks are a fifth generation, 5G, network and a fourth generation, 4G, network, respectively.

2. The method of claim 1, wherein the identifier is associated with the first network.

3. The method of claim 1, further comprising:

the second network device is selected based on the identity of the terminal.

4. The method of claim 1, further comprising:

a third message is received from the second network device, wherein the third message includes a request to log off the terminal from the first network.

5. The method of claim 4, wherein the repository is updated by removing information corresponding to the terminal being registered in the first network.

6. The method of claim 5, wherein the first message is received from a third network device, wherein the method further comprises:

and sending a fourth message to the third network device, wherein the fourth message comprises the request to log off the terminal from the first network.

7. A wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method of any of claims 1 to 6.

8. A computer readable medium comprising computer readable program medium code stored in the computer readable medium, which when executed by a processor causes the processor to implement the method of any one of claims 1 to 6.