CN114980075A - Address allocation method, session management function entity and communication system - Google Patents

Address allocation method, session management function entity and communication system Download PDF

Info

Publication number
CN114980075A
CN114980075A CN202210479921.5A CN202210479921A CN114980075A CN 114980075 A CN114980075 A CN 114980075A CN 202210479921 A CN202210479921 A CN 202210479921A CN 114980075 A CN114980075 A CN 114980075A
Authority
CN
China
Prior art keywords
address
user terminal
entity
session
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210479921.5A
Other languages
Chinese (zh)
Inventor
刘浩
李建钊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN202210479921.5A priority Critical patent/CN114980075A/en
Publication of CN114980075A publication Critical patent/CN114980075A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/26Network addressing or numbering for mobility support
    • H04W8/28Number portability ; Network address portability

Abstract

The disclosure provides an address allocation method, a session management function entity and a communication system. The address allocation method comprises the following steps: extracting session parameters of a user terminal from a session creation request sent by an AMF entity; inquiring whether an address used by the user terminal is recorded according to the session parameters; if the used address of the user terminal is recorded, the used address is sent to the AMF entity, so that the AMF entity sends the used address to the user terminal, and the user terminal uses the used address to perform service access. The method and the device can realize that the user terminal can use the fixed IPv6 address every time the user terminal is on line.

Description

Address allocation method, session management function entity and communication system
Technical Field
The present disclosure relates to the field of communications, and in particular, to an address allocation method, a session management function entity, and a communication system.
Background
When a current 5G SA (standard, independent networking) Network creates a PDU (Protocol Data Unit) Session on line every time a user attaches to the Network and a PDU Session is created, a Session Management Function (SMF) Network element in a 5G Core (5G Core, 5G Core Network) allocates an IPv6 address segment to the user in a pre-configured address pool according to a user location and a Data Network Name (DNN) of the user PDU Session. The terminal randomly selects one IPv6 address from the allocated address field for service access, and the IP address used by the user in each access will change.
Disclosure of Invention
The inventor has noted that in the related art, the terminal randomly selects one of the IPv6 addresses in the assigned address field for service access, thereby causing the IP address used by the terminal to change each time the terminal accesses the network. I.e. no fixed IP address can be provided for a particular user.
Accordingly, the present disclosure provides an address allocation scheme that can satisfy the requirements of a specific user for a fixed IP address.
According to a first aspect of the embodiments of the present disclosure, there is provided an address allocation method, performed by a session management function, SMF, entity, including: extracting session parameters of a user terminal from a session creation request sent by an access and mobility management function (AMF) entity; inquiring whether an address used by the user terminal is recorded according to the session parameters; and if the used address of the user terminal is recorded, sending the used address to the AMF entity, so that the AMF entity sends the used address to the user terminal, and the user terminal utilizes the used address to perform service access.
In some embodiments, the session parameters comprise a terminal identity and a network identity of the user terminal.
In some embodiments, the terminal identity is an international mobile subscriber identity IMSI; the network identification is a data network name DNN.
In some embodiments, the session creation request is an Nsmf pdusesion CreateSMContext message.
In some embodiments, if the address used by the user terminal is not recorded, a user address reporting policy is sent to a user plane function UPF entity; allocating an IPv6 address segment with a preset prefix to the user terminal; sending the IPv6 address field to the AMF entity so that the AMF entity sends the IPv6 address field to the user terminal, and the user terminal selects an address in the IPv6 address field as a service address and utilizes the service address to access services; and after receiving the service address of the user terminal sent by the UPF entity, recording the service address and the session parameters, wherein the UPF entity acquires the service address according to the user address reporting strategy and reports the service address to the SMF entity.
In some embodiments, the sending the user address reporting policy to the user plane function UPF entity includes: and sending the user address reporting strategy to the UPF entity by utilizing a message forwarding control protocol (PFCP) session establishment request.
In some embodiments, the prefix is 64 in length.
According to a second aspect of the embodiments of the present disclosure, there is provided a session management function entity, including: the first processing module is configured to extract session parameters of the user terminal from a session creation request sent by an access and mobility management function (AMF) entity; a second processing module configured to query whether an address used by the user terminal is recorded according to the session parameters; and the third processing module is configured to send the used address to the AMF entity if the used address of the user terminal is recorded, so that the AMF entity sends the used address to the user terminal, and the user terminal performs service access by using the used address.
In some embodiments, the session parameters comprise a terminal identity and a network identity of the user terminal.
In some embodiments, the terminal identity is an international mobile subscriber identity, IMSI; the network identification is a data network name DNN.
In some embodiments, the session creation request is an Nsmf pdusesion CreateSMContext message.
In some embodiments, the session management function further comprises: a fourth processing module, configured to send a user address reporting policy to a user plane function UPF entity if an address used by the user terminal is not recorded, and allocate an IPv6 address segment with a preset prefix to the user terminal; a fifth processing module, configured to send the IPv6 address field to the AMF entity, so that the AMF entity sends the IPv6 address field to the user terminal, and the user terminal selects an address in the IPv6 address field as a service address and performs service access by using the service address; and a sixth processing module, configured to record the service address and the session parameter after receiving the service address of the user terminal sent by the UPF entity, where the UPF entity obtains the service address according to the user address reporting policy and reports the service address to the SMF entity.
In some embodiments, the fourth processing module is configured to send the user address reporting policy to the UPF entity using a packet forwarding control protocol, PFCP, session establishment request.
In some embodiments, the prefix is 64 in length.
According to a third aspect of the embodiments of the present disclosure, there is provided a session management function entity, including: a memory configured to store instructions; a processor coupled to the memory, the processor configured to perform a method implementing any of the embodiments described above based on instructions stored by the memory.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a communication system including: a session management function, SMF, entity as in any of the embodiments above; an access and mobility management function (AMF) entity configured to send a session creation request to the SMF entity, wherein the session creation request includes session parameters of a user terminal, and send an address used by the user terminal sent by the SMF entity to the user terminal; a user terminal configured to perform service access using the used address.
In some embodiments, the session parameters comprise a terminal identity and a network identity of the user terminal.
In some embodiments, the terminal identity is an international mobile subscriber identity, IMSI; the network identification is a data network name DNN.
In some embodiments, the session creation request is an Nsmf pdusesion CreateSMContext message.
In some embodiments, the system further comprises a User Plane Function (UPF) entity, wherein the AMF entity is configured to send the IPv6 address field sent by the SMF entity to the user terminal; the user terminal is configured to select an address in the IPv6 address field as a service address, and perform service access by using the service address; and the user plane function UPF entity is configured to receive a user address reporting strategy sent by the SMF entity, acquire the service address according to the user address reporting strategy and report the service address to the SMF entity.
In some embodiments, the UPF entity receives a user address reporting policy sent by the SMF entity using a Packet Forwarding Control Protocol (PFCP) session establishment request.
According to a fifth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the instructions, when executed by a processor, implement the method according to any one of the embodiments.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic flowchart of an address allocation method according to an embodiment of the present disclosure;
FIG. 2 is a flowchart illustrating an address assignment method according to another embodiment of the disclosure;
fig. 3 is a schematic structural diagram of an SMF entity according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of an SMF entity according to another embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an SMF entity according to yet another embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of a communication system according to another embodiment of the present disclosure;
fig. 8 is a flowchart illustrating an address assignment method according to another embodiment of the disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
The relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
Fig. 1 is a schematic flowchart of an address allocation method according to an embodiment of the present disclosure. In some embodiments, the following address assignment method is performed by the SMF entity.
In step 101, session parameters of the ue are extracted from a session creation request sent by an AMF (Access and Mobility Management Function) entity.
In some embodiments, the session creation request is an Nsmf pdusesion _ CreateSMContext message.
In some embodiments, the session parameters include a terminal identification and a network identification of the user terminal.
For example, the terminal identifier is IMSI (International Mobile Subscriber Identity) and the network identifier is DNN.
For example, the IMSI of the user terminal is: 460111000010000. DNN is: 5 gzx.
In step 102, it is queried whether an address used by the user terminal is recorded according to the session parameters.
For example, whether an address used by the user terminal is recorded in the cache is queried according to the session parameters.
In step 103, if the used address of the user terminal is recorded, the used address of the user terminal is sent to the AMF entity, so that the AMF entity sends the used address of the user terminal to the user terminal, and the user terminal uses the used address to perform service access.
In the address allocation method provided by the above embodiment of the present disclosure, when a user terminal is online, an IPv6 address used by the user terminal is allocated to the user terminal, so as to meet the requirement of a specific user for a fixed IP address.
Fig. 2 is a flowchart illustrating an address assignment method according to another embodiment of the disclosure. In some embodiments, the following address assignment method is performed by the SMF entity.
In step 201, session parameters of the user terminal are extracted from the session creation request sent by the AMF entity.
In some embodiments, the session creation request is an Nsmf pdusessioncreatesmcontext message.
In some embodiments, the session parameters include a terminal identification and a network identification of the user terminal.
For example, the terminal identity is IMSI and the network identity is DNN.
For example, the IMSI of the user terminal is: 460111000010000. DNN is: 5 gzx.
In step 202, it is queried according to the session parameters whether an address used by the user terminal is recorded.
For example, whether an address used by the user terminal is recorded in the cache is queried according to the session parameters.
In step 203, if the address used by the User terminal is not recorded, a User address reporting policy is sent to a User Plane Function (UPF) entity.
In some embodiments, a PFCP (Packet Forwarding Control Protocol) Session Establishment request is used to send a user address reporting policy to the UPF entity.
In step 204, an IPv6 address field with a preset prefix is allocated to the user terminal.
In some embodiments, the prefix is 64 in length.
For example, the IPv6 address segment is: and 240e, 0180, 0001, 0010 and/or 64.
In step 205, the IPv6 address field is sent to the AMF entity, so that the AMF entity sends the IPv6 address field to the user terminal, and the user terminal selects an address in the IPv6 address field as a service address, and performs service access by using the service address.
For example, the user terminal selects one of the following addresses in the IPv6 address field as the service address:
240e:0180:0001:0010:000F:000F:000F:000F
in step 206, after receiving the service address of the user terminal sent by the UPF entity, the service address and the session parameters are recorded, wherein the UPF entity obtains the service address according to the user address reporting policy and reports the service address to the SMF entity.
The requirement of a specific user on a fixed IP address is met by recording the IPv6 address used by the user terminal, so that when the user terminal is on line again, the service address used by the user terminal is distributed to the user terminal.
Fig. 3 is a schematic structural diagram of an SMF entity according to an embodiment of the present disclosure. As shown in fig. 3, the SMF entity includes a first processing module 31, a second processing module 32, and a third processing module 33.
The first processing module 31 is configured to extract session parameters of the user terminal from a session creation request sent by the access and mobility management function AMF entity.
In some embodiments, the session creation request is an Nsmf pdusesion _ CreateSMContext message.
In some embodiments, the session parameters include a terminal identification and a network identification of the user terminal.
For example, the terminal identity is IMSI and the network identity is DNN.
For example, the IMSI of the user terminal is: 460111000010000. DNN is: 5 gzx.
The second processing module 32 is configured to query whether an address used by the user terminal is recorded according to the session parameter.
For example, the second processing module 32 inquires in the cache whether an address used by the user terminal is recorded according to the session parameter.
The third processing module 33 is configured to send the used address to the AMF entity if the used address of the user terminal is recorded, so that the AMF entity sends the used address to the user terminal, and the user terminal uses the used address for service access.
Fig. 4 is a schematic structural diagram of an SMF entity according to another embodiment of the present disclosure. Fig. 4 differs from fig. 3 in that in the embodiment shown in fig. 4, the SMF entity further comprises a fourth processing module 34, a fifth processing module 35 and a sixth processing module 36.
The fourth processing module 34 is configured to send the user address reporting policy to the user plane function UPF entity if the address used by the user terminal is not recorded, and allocate an IPv6 address field with a preset prefix to the user terminal.
In some embodiments, the fourth processing module 34 sends the user address reporting policy to the UPF entity by using a PFCP Session Establishment request.
In some embodiments, the prefix is 64 in length.
For example, the IPv6 address segment is: 240e, 0180, 0001, 0010, and/64.
The fifth processing module 35 is configured to send the IPv6 address field to the AMF entity, so that the AMF entity sends the IPv6 address field to the user terminal, and the user terminal selects an address in the IPv6 address field as a service address, and performs service access by using the service address.
For example, the user terminal selects one of the following addresses in the IPv6 address field as the service address:
240e:0180:0001:0010:000F:000F:000F:000F
the sixth processing module 36 is configured to record the service address and the session parameter after receiving the service address of the user terminal sent by the UPF entity, where the UPF entity obtains the service address according to the user address reporting policy and reports the service address to the SMF entity.
Fig. 5 is a schematic structural diagram of an SMF entity according to yet another embodiment of the present disclosure. As shown in fig. 5, the SMF entity includes a memory 51 and a processor 52.
The memory 51 is used for storing instructions, the processor 52 is coupled to the memory 51, and the processor 52 is configured to execute the method according to any one of the embodiments in fig. 1 or fig. 2 based on the instructions stored in the memory.
As shown in fig. 5, the SMF entity further includes a communication interface 53 for information interaction with other devices. Meanwhile, the SMF entity further includes a bus 54, and the processor 52, the communication interface 53, and the memory 51 communicate with each other through the bus 54.
The memory 51 may comprise a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 51 may also be a memory array. The storage 51 may also be partitioned and the blocks may be combined into virtual volumes according to certain rules.
Further, the processor 52 may be a central processing unit CPU, or may be an application specific integrated circuit ASIC, or one or more integrated circuits configured to implement embodiments of the present disclosure.
The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the instructions, when executed by a processor, implement a method according to any one of the embodiments shown in fig. 1 or fig. 2.
Fig. 6 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure. As shown in fig. 6, the communication system includes an SMF entity 61, an AMF entity 62, and a user terminal 63. The SMF entity 61 is an SMF entity according to any of the embodiments in fig. 3-5.
The AMF entity 62 is configured to send a session creation request to the SMF entity 61, where the session creation request includes session parameters of the user terminal, and also send an address used by the user terminal sent by the SMF entity 61 to the user terminal 63.
In some embodiments, the session creation request is an Nsmf pdusesion _ CreateSMContext message.
In some embodiments, the session parameters include a terminal identification and a network identification of the user terminal.
For example, the terminal identity is IMSI and the network identity is DNN.
For example, the IMSI of the user terminal is: 460111000010000. DNN is: 5 gzx.
The user terminal 63 is configured to make service access using the used address.
Fig. 7 is a schematic structural diagram of a communication system according to another embodiment of the present disclosure. Fig. 7 differs from fig. 6 in that in the embodiment shown in fig. 7 the communication system further comprises a UPF entity 64.
The AMF entity 62 is configured to send the IPv6 address field sent by the SMF entity 61 to the user terminal 63.
The user terminal 63 is configured to select an address in the IPv6 address field as a service address, and perform service access using the service address.
The UPF entity 64 is configured to receive the user address reporting policy sent by the SMF entity 61, obtain a service address used by the user terminal 63 according to the user address reporting policy, and report the service address to the SMF entity 61.
In some embodiments, the UPF entity 64 requests to receive the user address reporting policy sent by the SMF entity by using a PFCP Session Establishment.
Fig. 8 is a flowchart illustrating an address assignment method according to another embodiment of the disclosure.
In step 801, the AMF entity sends a session creation request to the SMF entity.
In some embodiments, the session creation request is an Nsmf pdusesion _ CreateSMContext message.
In step 802, the SMF entity extracts the session parameters of the user terminal from the session creation request, and inquires whether an address used by the user terminal is recorded according to the session parameters.
In some embodiments, the session parameters include a terminal identification and a network identification of the user terminal.
For example, the terminal identity is IMSI and the network identity is DNN.
For example, the IMSI of the user terminal is: 460111000010000. DNN is: 5 gzx.
In some embodiments, the SMF entity queries in the cache whether an address used by the user terminal is recorded according to the session parameters.
In step 803, if no address used by the user terminal is recorded, the SMF entity sends a user address reporting policy to the UPF entity.
In some embodiments, the user address reporting policy is sent to the UPF entity using a PFCP Session Establishment request.
In step 804, the SMF entity assigns an IPv6 address field having a preset prefix to the user terminal.
In some embodiments, the prefix is 64 in length.
For example, the IPv6 address segment is: and 240e, 0180, 0001, 0010 and/or 64.
In step 805, the SMF entity sends the IPv6 address segment to the AMF entity.
The AMF entity sends the IPv6 address fragment to the user terminal in step 806.
In step 807, the user terminal selects an address in the IPv6 address field as a service address.
For example, the user terminal selects one of the following addresses in the IPv6 address field as the service address:
240e:0180:0001:0010:000F:000F:000F:000F
in step 808, the user terminal performs service access using the service address.
In step 809, the UPF entity obtains the service address used by the user terminal according to the user address reporting policy.
In step 810, the UPF entity reports the service address used by the user terminal to the SMF entity.
In step 811, the SMF entity records the service address and the session parameters.
In step 812, when the user terminal comes online again, the AMF entity sends a session creation request to the SMF entity again.
In step 813, the SMF entity extracts the session parameter of the user terminal from the session creation request and inquires whether an address used by the user terminal is recorded according to the session parameter.
In step 814, if the address used by the user terminal is recorded, the SMF entity sends the address used by the user terminal to the AMF entity.
The AMF entity transmits the address used by the user terminal to the user terminal in step 815.
In step 816, the user terminal performs service access using the used address.
By implementing the above embodiments of the present disclosure, the following beneficial effects can be obtained:
1. when the user terminal is on line each time, the SMF entity can distribute the fixed IP address to the user terminal, so that the user terminal uses the fixed IP address to access the service, and the requirement of a private line client on the fixed IP is met.
2. The private line client can inquire the user IP address of the private line user to the SMF entity in real time, and the client intranet can actively initiate a downlink request to the online private line user so as to meet diversified service requirements of the private line client.
In some embodiments, the functional units described above can be implemented as general purpose processors, Programmable Logic Controllers (PLCs), Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable Logic devices, discrete Gate or transistor Logic devices, discrete hardware components, or any suitable combination thereof for performing the functions described in this disclosure.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk.
The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

Claims (22)

1. An address allocation method, performed by a session management function, SMF, entity, comprising:
extracting session parameters of a user terminal from a session creation request sent by an access and mobility management function (AMF) entity;
inquiring whether an address used by the user terminal is recorded according to the session parameters;
and if the used address of the user terminal is recorded, sending the used address to the AMF entity, so that the AMF entity sends the used address to the user terminal, and the user terminal utilizes the used address to perform service access.
2. The method of claim 1, wherein,
the session parameters include a terminal identifier and a network identifier of the user terminal.
3. The method of claim 2, wherein,
the terminal identification is an International Mobile Subscriber Identity (IMSI);
the network identification is a data network name DNN.
4. The method of claim 1, wherein,
the session creation request is an Nsmf _ PDUSession _ CreateSMContext message.
5. The method of any of claims 1-4, further comprising:
if the address used by the user terminal is not recorded, sending a user address reporting strategy to a user plane function UPF entity;
allocating an IPv6 address segment with a preset prefix to the user terminal;
sending the IPv6 address field to the AMF entity so that the AMF entity sends the IPv6 address field to the user terminal, and the user terminal selects an address from the IPv6 address field as a service address and utilizes the service address to carry out service access;
and after receiving the service address of the user terminal sent by the UPF entity, recording the service address and the session parameters, wherein the UPF entity acquires the service address according to the user address reporting strategy and reports the service address to the SMF entity.
6. The method of claim 5, wherein the sending the user address reporting policy to the UPF entity comprises:
and sending the user address reporting strategy to the UPF entity by utilizing a message forwarding control protocol (PFCP) session establishment request.
7. The method of claim 5, wherein,
the prefix is 64 in length.
8. A session management function entity, comprising:
the first processing module is configured to extract session parameters of the user terminal from a session creation request sent by an access and mobility management function (AMF) entity;
a second processing module configured to query whether an address used by the user terminal is recorded according to the session parameters;
and the third processing module is configured to send the used address to the AMF entity if the used address of the user terminal is recorded, so that the AMF entity sends the used address to the user terminal, and the user terminal performs service access by using the used address.
9. The session management function entity of claim 8,
the session parameters include a terminal identifier and a network identifier of the user terminal.
10. The session management function entity of claim 9, wherein,
the terminal identification is an International Mobile Subscriber Identity (IMSI);
the network identification is a data network name DNN.
11. The session management function entity of claim 8,
the session creation request is an Nsmf _ pdusesion _ CreateSMContext message.
12. The session management function entity of any of claims 8-11, further comprising:
a fourth processing module, configured to send a user address reporting policy to a user plane function UPF entity if an address used by the user terminal is not recorded, and allocate an IPv6 address segment with a preset prefix to the user terminal;
a fifth processing module, configured to send the IPv6 address field to the AMF entity, so that the AMF entity sends the IPv6 address field to the user terminal, and the user terminal selects an address in the IPv6 address field as a service address and performs service access by using the service address;
and a sixth processing module, configured to record the service address and the session parameter after receiving the service address of the user terminal sent by the UPF entity, where the UPF entity obtains the service address according to the user address reporting policy and reports the service address to the SMF entity.
13. The session management function entity of claim 12,
the fourth processing module is configured to send the user address reporting policy to the UPF entity using a packet forwarding control protocol, PFCP, session establishment request.
14. The session management function entity of claim 12,
the prefix is 64 in length.
15. A session management function entity, comprising:
a memory configured to store instructions;
a processor coupled to the memory, the processor configured to perform an implementation of the method recited in any one of claims 1-7 based on instructions stored by the memory.
16. A communication system, comprising:
a session management function, SMF, entity according to any of claims 8-17;
an access and mobility management function (AMF) entity configured to send a session creation request to the SMF entity, wherein the session creation request includes session parameters of a user terminal, and send an address used by the user terminal sent by the SMF entity to the user terminal;
a user terminal configured to perform service access using the used address.
17. The system of claim 16, wherein,
the session parameters include a terminal identifier and a network identifier of the user terminal.
18. The system of claim 17, wherein,
the terminal identification is an International Mobile Subscriber Identity (IMSI);
the network identification is a data network name DNN.
19. The system of claim 16, wherein,
the session creation request is an Nsmf _ pdusesion _ CreateSMContext message.
20. The system according to any of claims 16-19, further comprising a user plane function, UPF, entity, wherein,
the AMF entity is configured to send the IPv6 address field sent by the SMF entity to the user terminal;
the user terminal is configured to select an address in the IPv6 address field as a service address, and perform service access by using the service address;
and the user plane function UPF entity is configured to receive a user address reporting strategy sent by the SMF entity, acquire the service address according to the user address reporting strategy and report the service address to the SMF entity.
21. The system of claim 20, wherein,
and the UPF entity utilizes a message forwarding control protocol (PFCP) session establishment request to receive a user address reporting strategy sent by the SMF entity.
22. A non-transitory computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions which, when executed by a processor, implement the method of any one of claims 1-7.
CN202210479921.5A 2022-05-05 2022-05-05 Address allocation method, session management function entity and communication system Pending CN114980075A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210479921.5A CN114980075A (en) 2022-05-05 2022-05-05 Address allocation method, session management function entity and communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210479921.5A CN114980075A (en) 2022-05-05 2022-05-05 Address allocation method, session management function entity and communication system

Publications (1)

Publication Number Publication Date
CN114980075A true CN114980075A (en) 2022-08-30

Family

ID=82981642

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210479921.5A Pending CN114980075A (en) 2022-05-05 2022-05-05 Address allocation method, session management function entity and communication system

Country Status (1)

Country Link
CN (1) CN114980075A (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110049504A (en) * 2018-01-15 2019-07-23 华为技术有限公司 A kind of conversation managing method and device
CN110120988A (en) * 2018-02-07 2019-08-13 华为技术有限公司 Address management method, equipment and system
WO2019158010A1 (en) * 2018-02-13 2019-08-22 华为技术有限公司 Resource management method, device and system
CN112235776A (en) * 2020-08-31 2021-01-15 北京中科晶上科技股份有限公司 Method for allocating IP address field according to needs and IP address statistical system
CN112437456A (en) * 2020-12-07 2021-03-02 中国联合网络通信集团有限公司 Communication method and device in non-public network
JP2021077995A (en) * 2019-11-08 2021-05-20 株式会社Nttドコモ Communication control apparatus
CN113382468A (en) * 2021-06-24 2021-09-10 深圳艾灵网络有限公司 Address allocation method for local network device, electronic device, and storage medium
CN114039947A (en) * 2020-07-21 2022-02-11 中国电信股份有限公司 Terminal address allocation method, UPF, system and storage medium
US20220078606A1 (en) * 2018-12-04 2022-03-10 Nokia Technologies Oy Apparatus, method and computer program
CN114189851A (en) * 2021-11-30 2022-03-15 中国电信股份有限公司 IP address allocation method, SMF and storage medium

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110049504A (en) * 2018-01-15 2019-07-23 华为技术有限公司 A kind of conversation managing method and device
CN110120988A (en) * 2018-02-07 2019-08-13 华为技术有限公司 Address management method, equipment and system
WO2019158010A1 (en) * 2018-02-13 2019-08-22 华为技术有限公司 Resource management method, device and system
US20220078606A1 (en) * 2018-12-04 2022-03-10 Nokia Technologies Oy Apparatus, method and computer program
JP2021077995A (en) * 2019-11-08 2021-05-20 株式会社Nttドコモ Communication control apparatus
CN114039947A (en) * 2020-07-21 2022-02-11 中国电信股份有限公司 Terminal address allocation method, UPF, system and storage medium
CN112235776A (en) * 2020-08-31 2021-01-15 北京中科晶上科技股份有限公司 Method for allocating IP address field according to needs and IP address statistical system
CN112437456A (en) * 2020-12-07 2021-03-02 中国联合网络通信集团有限公司 Communication method and device in non-public network
CN113382468A (en) * 2021-06-24 2021-09-10 深圳艾灵网络有限公司 Address allocation method for local network device, electronic device, and storage medium
CN114189851A (en) * 2021-11-30 2022-03-15 中国电信股份有限公司 IP address allocation method, SMF and storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE等: "Pseudo-CR on evaluation and conclusions for key issue #4", 3GPP TSG-CT WG4 MEETING #106-E C4-215534, 15 October 2021 (2021-10-15), pages 7 *

Similar Documents

Publication Publication Date Title
US9210124B2 (en) Method, apparatus, and system for allocating public IP address
US9560492B2 (en) Method for allocating identification, method for paging group, and communication device
KR100657316B1 (en) A fast handover method in DHCPv4, handover apparatus thereof and recording medium thereof
JP7260230B2 (en) Alias-based addressing calling method and apparatus
WO2017206572A1 (en) Ip address management method for use in network environment having multiple dhcp servers, and dhcp client
EP3742785B1 (en) Session management method and device
CN114039947B (en) Terminal address allocation method, UPF, system and storage medium
US20190208572A1 (en) Method for dynamically creating local packet data network, apparatus, and system
CN112437456A (en) Communication method and device in non-public network
US20190037485A1 (en) Service node selection and query method, apparatus, and system
US20210250844A1 (en) Routing management method and apparatus
CN107645722B (en) Private network selective access method and system, public network MME, HSS and base station
CN105142189B (en) The roam control method and device of website
CN114189851A (en) IP address allocation method, SMF and storage medium
WO2014101240A1 (en) Data storage method and apparatus, data operation method and system, and access server
CN112217653B (en) Strategy issuing method, device and system
WO2019047611A1 (en) Data transmission method, pnf sdn controller, vnf sdn controller, and system
US10863555B2 (en) Access method, apparatus, device, and system
KR101978705B1 (en) Registration area determining method and mobility management entity
CN111953806B (en) Link selection method, device, computer equipment and computer storage medium
CN103379479B (en) A kind of determine ID and the method for notifying parameters information, system and equipment
CN106375489B (en) Method and device for processing Media Access Control (MAC) address
CN114980075A (en) Address allocation method, session management function entity and communication system
CN109167759B (en) Mobile phone number acquisition method and device
CN111479296A (en) CDN cache server selection method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination