Communication method and device for network device session management, and medium

Abstract

The embodiment of the invention relates to a communication method, communication equipment, a medium and a program product. In the method, an access network device sends a first request to an access and mobility management function (AMF), the first request is used for requesting to establish a session between the access network device and a user plane function (UPF), and the first request comprises identification information of the access network device. Then, the access network device receives first configuration information for the session from a session management function (SMF) via the AMF, the first configuration information comprising configuration information for an uplink channel from the access network device to the UPF. In this way, the access network device can actively initiate a session establishment process between the access network device and the UPF, and finally establishes a data path between the access network device and the UPF.

Description

Communication method, device and medium for network device session management Technical Field

[0001] Embodiments of the present disclosure relate to the field of electronics, and more particularly, to a communication method, a communication device, a communication system, a computer-readable storage medium, and a computer program product for managing a network device session. Background Art

[0002] With the reduction in computing and storage costs and the emergence of a large number of low-latency services and local applications, computing and storage, as well as the intelligent algorithms that rely on them, are trending towards deployment at the network edge, close to the data source, thus forming a data-centric network architecture. The fundamental function of mobile communication networks will also begin to shift from being a pipeline for information transmission to a platform for data management and control. In some applications, sixth-generation (6G) communication networks act as both producers and providers of data, providing trusted data services for intelligent applications, while also acting as consumers of data, leveraging data-driven intelligent applications to improve network performance and operational efficiency. However, the network architecture and service processes of fifth-generation (5G) communication networks struggle to support the many new services of 6G communication networks. For example, the user plane of 5G communication networks cannot support "path-associated computing" and "arbitrary topology," making the 5G user plane unsuitable for carrying the services and data required for 6G.

[0003] Summary of the Invention

[0004] In view of this, embodiments of the present disclosure provide a communication method, a communication device, a communication system, and a computer-readable storage medium, thereby resolving a data service scenario in which conventional session mechanisms cannot support data generated by access network devices.

[0005] In a first aspect of the present disclosure, a method for managing a network device session is provided. The method includes: sending a first request to an access and mobility management function (AMF), the first request being used to request establishment of a session between an access network device and a user plane function (UPF), the first request including identification information of the access network device; and receiving first configuration information from a session management function (SMF) via the AMF, the first configuration information including configuration information for an uplink channel from the access network device to the UPF. In this manner, the access network device can proactively initiate the session establishment process between the access network device and the UPF, ultimately establishing a data path between the access network device and the UPF.

[0006] In some embodiments, the first request also includes at least one of the following: information indicating the device initiating the first request; or identification information of the data service task associated with the first request. This allows for establishing a session with the access network device. By using the information indicating the device initiating the first request, the conventional session mechanism between the terminal device and the UPF can be reused without redesigning the session policy, thereby reducing resource consumption.

[0007] In some embodiments, the first request also includes identification information of a data service task associated with the first request, and the identification information of the data service task includes information indicating the device initiating the first request. This allows for establishing a session with the access network device. By using the information indicating the device initiating the first request, the conventional session mechanism between the terminal device and the UPF can be reused without redesigning the session policy, thereby reducing resource consumption.

[0008] In some embodiments, the method further includes: sending a second request to the AMF, the second request being for requesting release of the session between the access network device and the UPF, the second request including session identification information; and receiving a response message corresponding to the second request from the SMF via the AMF. Thus, the session between the access network device and the UPF can be released.

[0009] In some embodiments, the method further includes: sending a third request to the AMF, the third request being used to request registration of the access network device, the third request including identification information of the access network device; receiving from the AMF rule information for establishing a session; and receiving from the AMF a response message corresponding to the third request. Thus, the access network device can be registered, thereby facilitating subsequent establishment of a session between the access network device and the UPF.

[0010] In some embodiments, the method further includes: sending a fourth request to the AMF, the fourth request being for requesting deregistration of the access network device, the deregistration request including identification information of the access network device; and receiving a response message corresponding to the fourth request from the AMF. Thus, deregistration of the access network device can be achieved with reduced signaling overhead.

[0011] In some embodiments, the first request is sent via the N2 interface, and the first configuration information is received via the N2 interface. Thus, a session establishment process initiated by the access network device can be implemented.

[0012] In a second aspect of the present disclosure, a method for managing a network device session is provided. The method includes: receiving a first request from an access network device to establish a session between the access network device and a user plane function (UPF), the first request including identification information of the access network device; and sending the first request to a session management function (SMF). In this manner, a session establishment process initiated by the access network device between the access network device and the UPF can be established with low signaling overhead, ultimately establishing a data path between the access network device and the UPF.

[0013] In some embodiments, the first request also includes at least one of the following: information indicating the device initiating the first request; or identification information of the data service task associated with the first request. This allows for establishing a session with the access network device. By using the information indicating the device initiating the first request, the conventional session mechanism between the terminal device and the UPF can be reused without redesigning the session policy, thereby reducing resource consumption.

[0014] In some embodiments, the first request also includes identification information of a data service task associated with the first request, and the identification information of the data service task includes information indicating the device initiating the first request. This allows for establishing a session with the access network device. By using the information indicating the device initiating the first request, the conventional session mechanism between the terminal device and the UPF can be reused without redesigning the session policy, thereby reducing resource consumption.

[0015] In some embodiments, the method further includes: receiving a third request from the access network device, the third request being used to request registration of the access network device, the third request including identification information of the access network device; configuring context information of the access network device based on the third request; sending a third request to the core network device, the core network device being used to manage subscription data associated with the access network device; receiving a response message corresponding to the third request from the core network device; sending a fifth request associated with the access network device to the policy control function (PCF), the fifth request being used to request rule information associated with the access network device; receiving rule information for establishing a session from the PCF; sending rule information for establishing a session to the access network device; and sending a response message corresponding to the third request to the access network device. Thus, the access network device can be registered with lower signaling overhead, thereby facilitating subsequent establishment of a session between the access network device and the UPF.

[0016] In some embodiments, the method further includes: receiving a sixth request associated with the access network device from the core network device, the sixth request being used to request configuration of context information for the access network device, the core network device being used to manage subscription data associated with the access network device; configuring the context information of the access network device based on the sixth request; sending a response message corresponding to the sixth request to the core network device; sending a fifth request associated with the access network device to the PCF, the fifth request being used to request rule information associated with the access network device; receiving rule information for establishing a session from the PCF; and sending rule information for establishing a session to the access network device. Thus, the access network device can be registered with lower signaling overhead, thereby facilitating subsequent establishment of a session between the access network device and the UPF.

[0017] In some embodiments, the method further includes: receiving a fourth request from the access network device, the fourth request being used to request deregistration of the access network device, the fourth request including identification information of the access network device; sending a fourth request to a core network device, the core network device being used to manage subscription data associated with the access network device; receiving a response message corresponding to the fourth request from the core network device; sending a seventh request associated with the access network device to the PCF, the sixth request being used to request release of rule information for a session between the access network device and the UPF; receiving a response message corresponding to the seventh request from the PCF; sending a response message corresponding to the fourth request to the access network device; and releasing context information of the access network device. Thus, the access network device can be deregistered with low signaling overhead.

[0018] In some embodiments, the method further includes: receiving a second request from the access network device, the second request including identification information of the session; and sending the second request to the SMF. In this way, the session between the access network device and the user plane function (UPF) can be deleted with low signaling overhead.

[0019] In a third aspect of the present disclosure, a method for managing a network device session is provided. The method includes: receiving a first request from an access and mobility management function (AMF) to establish a session between an access network device and a user plane function (UPF), the first request including identification information of the access network device; and sending, via the AMF, first configuration information to the access network device, the first configuration information including configuration information for an uplink channel from the access network device to the UPF. In this way, a session establishment process initiated by the access network device between the access network device and the UPF can be established with low signaling overhead, ultimately establishing a data path between the access network device and the UPF.

[0020] In some embodiments, the first request also includes at least one of the following: information indicating the device initiating the first request; or identification information of the data service task associated with the first request. This allows for establishing a session with the access network device. By using the information indicating the device initiating the first request, the conventional session mechanism between the terminal device and the UPF can be reused without redesigning the session policy, thereby reducing resource consumption.

[0021] In some embodiments, the first request also includes identification information of a data service task associated with the first request, and the identification information of the data service task includes information indicating the device initiating the first request. This allows for establishing a session with the access network device. By using the information indicating the device initiating the first request, the conventional session mechanism between the terminal device and the UPF can be reused without redesigning the session policy, thereby reducing resource consumption.

[0022] In some embodiments, the method further includes: based on determining that the indication information of the device is access network device indication information, sending an eighth request associated with the access network device to the core network device, the eighth request being used to request subscription data associated with the access network device, the core network device being used to manage the subscription data associated with the access network device; and receiving the subscription data from the core network device. This enables authentication of the access network device, thereby improving communication security.

[0023] In some embodiments, the method further includes: receiving a second request from the AMF, the second request being for requesting release of a session between the access network device and the UPF, the second request including session identification information; sending, via the AMF, an indication to release the session to the access network device and the UPF; sending, via the AMF, a response message corresponding to the second request to the access network device; and releasing context information associated with the session. Thus, the session between the access network device and the user plane function (UPF) can be deleted with reduced signaling overhead.

[0024] In a fourth aspect of the present disclosure, a method for managing a network device session is provided. The method includes: sending a third request to an access and mobility management function (AMF), the third request being for registering an access network device and including identification information of the access network device; receiving from the AMF rule information for establishing a session; and receiving from the AMF a response message corresponding to the third request. In this manner, the access network device can be registered with low signaling overhead, thereby facilitating subsequent session establishment between the access network device and the UPF.

[0025] In some embodiments, the method further includes: sending a fourth request to the AMF, the fourth request being for requesting deregistration of the access network device, the fourth request including identification information of the access network device; and receiving a response message corresponding to the fourth request from the AMF. Thus, deregistration of the access network device can be achieved with reduced signaling overhead.

[0026] In a fifth aspect of the present disclosure, a method for managing a network device session is provided. The method includes: receiving a third request for registering an access network device, the third request including identification information of the access network device; and storing context information associated with the access network device, the context information being used to support a session between the access network device and a user plane function (UPF). In this manner, the access network device can be registered with low signaling overhead, thereby facilitating subsequent session establishment between the access network device and the UPF.

[0027] In some embodiments, the third request is received from an operations, administration, and maintenance (OAM) device, and the method further includes: sending a sixth request associated with the access network device to the AMF, the sixth request being used to request configuration of context information for the access network device; receiving a response message corresponding to the sixth request from the AMF; and sending a ninth request associated with the access network device to the PCF, the ninth request being used to request update of rule information associated with the access network device. Thus, context configuration and policy update of the access network device can be performed, thereby facilitating subsequent establishment of a session between the access network device and the UPF.

[0028] In some embodiments, the method further includes: receiving a fourth request from the AMF, the fourth request including identification information of the access network device; releasing context information associated with the access network device; and sending a response message corresponding to the fourth request to the AMF. Thus, the access network device can be deregistered with low signaling overhead.

[0029] In some embodiments, the method further includes: receiving an eighth request associated with the access network device from a session management function (SMF), the eighth request being for subscription data associated with the access network device; and sending the subscription data associated with the access network device to the SMF. Thus, the access network device can be authenticated with lower signaling overhead, thereby improving communication security.

[0030] In a sixth aspect of the present disclosure, a communication device is provided. The device includes a processor connected to a memory, the memory storing instructions that, when executed by the processor, cause the device to perform the method according to the first aspect or any embodiment thereof. In some embodiments, the device further includes the memory.

[0031] In some embodiments, the device is a chip.

[0032] In a seventh aspect of the present disclosure, a communication device is provided, comprising a processor connected to a memory storing instructions that, when executed by the processor, cause the device to perform the method according to the second aspect or any embodiment thereof.

[0033] In some embodiments, the device further comprises the memory.

[0034] In some embodiments, the device is a chip.

[0035] In an eighth aspect of the present disclosure, a communication device is provided, comprising a processor connected to a memory storing instructions that, when executed by the processor, cause the device to perform the method according to the third aspect or any embodiment thereof.

[0036] In some embodiments, the device further comprises the memory.

[0037] In some embodiments, the device is a chip.

[0038] In a ninth aspect of the present disclosure, a communication device is provided, comprising a processor connected to a memory storing instructions that, when executed by the processor, cause the device to perform the method according to the fourth aspect or any embodiment thereof.

[0039] In some embodiments, the device further comprises the memory.

[0040] In some embodiments, the device is a chip.

[0041] In a tenth aspect of the present disclosure, a communication device is provided, comprising a processor connected to a memory storing instructions, which, when executed by the processor, cause the device to perform the method according to the fifth aspect or any embodiment thereof.

[0042] In some embodiments, the device further comprises the memory.

[0043] In some embodiments, the device is a chip.

[0044] In an eleventh aspect of the present disclosure, a system is provided, comprising the communication device according to the fifth aspect, the communication device according to the sixth aspect, the communication device according to the seventh aspect, the communication device according to the eighth aspect, and the communication device according to the tenth aspect.

[0045] In a twelfth aspect of the present disclosure, a computer-readable storage medium is provided, which stores instructions that, when run, enable the method according to any one of the first to fifth aspects or any embodiment thereof to be executed.

[0046] In the thirteenth aspect of the present disclosure, a computer program product is provided, which includes instructions. When the instructions are executed on a computer, the computer executes the method according to any one of the first to fifth aspects or any embodiment thereof.

[0047] It should be understood that the contents described in the Summary of the Invention section are not intended to limit the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0049] FIG1A shows a schematic diagram of a network environment according to some embodiments of the present disclosure;

[0050] FIG1B illustrates a schematic diagram of a 6G mobile communication network data plane functional architecture provided for some embodiments of the present disclosure;

[0051] FIG2A shows an interactive signaling diagram of a method for registering an access network device according to some embodiments of the present disclosure;

[0052] FIG2B shows an interactive signaling diagram of a method for establishing a session according to some embodiments of the present disclosure;

[0053] FIG3A shows an interactive signaling diagram of an example implementation of a method for registration of an access network device according to some embodiments of the present disclosure;

[0054] FIG3B shows an interactive signaling diagram of another example implementation of a method for registration of an access network device according to some embodiments of the present disclosure;

[0055] FIG4 shows an interactive signaling diagram of an example implementation of a method for deregistration of an access network device according to some embodiments of the present disclosure;

[0056] FIG5A illustrates an interaction signaling diagram of an example implementation of a method for establishing a session according to some embodiments of the present disclosure;

[0057] FIG5B shows an interaction signaling diagram of another example implementation of a method for establishing a session according to some embodiments of the present disclosure;

[0058] FIG5C shows an interaction signaling diagram of yet another example implementation of a method for establishing a session according to some embodiments of the present disclosure;

[0059] FIG6 illustrates an interaction signaling diagram of an example implementation of a method for deleting a session according to some embodiments of the present disclosure;

[0060] FIG7 shows a schematic flow chart of a method implemented at an access network device according to some embodiments of the present disclosure;

[0061] FIG8 shows a schematic flow chart of another method implemented at an access network device according to some embodiments of the present disclosure;

[0062] FIG9 shows a schematic flow chart of a method implemented at an AMF according to some embodiments of the present disclosure;

[0063] FIG10 shows a schematic flow chart of a method implemented at an SMF according to some embodiments of the present disclosure;

[0064] FIG11 shows a schematic flow chart of a method implemented at a data management core network device according to some embodiments of the present disclosure;

[0065] FIG12 is a schematic diagram of the main components of an example device of a possible implementation method according to an embodiment of the present disclosure; and

[0066] FIG13 is a simplified block diagram of an example device for one possible implementation of an embodiment of the present disclosure. DETAILED DESCRIPTION

[0067] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0068] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. can refer to different or the same objects. The term "and / or" means at least one of the two items it is associated with. For example, "A and / or B" means A, B, or A and B. Other explicit and implicit definitions may also be included below.

[0069] Embodiments of the present disclosure may be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols such as third generation (3G), fourth generation (4G), fifth generation (5G) and future communication protocols (e.g., sixth generation (6G)), wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future.

[0070] The technical solutions of the embodiments of the present disclosure are applied to communication systems that follow any appropriate communication protocols, such as: long term evolution (LTE) systems, wideband code division multiple access systems (WCDMA), code division multiple access 2000 systems (CDMA2000), time division-Synchronization Code Division Multiple Access systems (TD-SCDMA), frequency division duplex (FDD) systems, time division duplex (TDD), fifth generation (5G) systems (e.g., new radio (NR)) and future communication systems (e.g., sixth generation (6G) systems), etc.

[0071] For the purpose of explanation, the following is referred to as the Third Generation Partnership Project (3 rdThe embodiments of the present disclosure are described in the context of a cellular communication system in the 3GPP (3rd Generation Partnership Project). However, it should be understood that the embodiments of the present disclosure are not limited to this communication system, but can be applied to any communication system with similar problems, such as a wireless local area network (WLAN), a wired communication system, or other communication systems developed in the future.

[0072] The term "terminal" or "terminal device" used in this disclosure refers to any terminal device that can perform wired or wireless communication with network devices or with each other. Terminal devices may sometimes be referred to as user equipment or UE. Terminal devices may be any type of mobile terminal, fixed terminal or portable terminal. Terminal devices may be various wireless communication devices with wireless communication capabilities. With the rise of Internet of Things (IOT) technology, more and more devices that did not previously have communication capabilities, such as but not limited to household appliances, vehicles, tools and equipment, service equipment and service facilities, have begun to obtain wireless communication capabilities by configuring wireless communication units, so that they can access wireless communication networks and accept remote control. Such devices have wireless communication capabilities because they are configured with wireless communication units, and therefore also fall into the category of wireless communication devices. As an example, the terminal device may include a mobile cellular phone, a cordless phone, a mobile terminal (MT), a mobile station, a mobile device, a wireless terminal, a handheld device, a client, a subscription station, a portable subscription station, an Internet node, a communicator, a desktop computer, a laptop computer, a notebook computer, a tablet computer, a personal communication system device, a personal navigation device, a personal digital assistant (PDA), a wireless data card, a wireless modem (modulator demodulator, Modem), a positioning device, a radio broadcast receiver, an e-book device, a gaming device, an IoT device, an in-vehicle device, an aircraft, a virtual reality (VR) device, an augmented reality (AR) device, a wearable device (e.g., a smart watch, etc.), a terminal device in a 5G network or any terminal device in an evolved public land mobile network (PLMN), other devices that can be used for communication, or any combination thereof. The terminal device and the access network device communicate with each other using a certain air interface technology.

[0073] The term "network node" or "network device" used in this disclosure refers to an entity or node that can be used to communicate with a terminal device, for example, an access network device. An access network device can be a device deployed in a radio access network to provide wireless communication functions for a mobile terminal, for example, a radio access network (RAN) network device. Access network devices may include various types of base stations. The base station is used to provide wireless access services to terminal devices. Specifically, each base station corresponds to a service coverage area, and terminal devices entering the area can communicate with the base station through wireless signals to receive the wireless access services provided by the base station. There may be overlap between the service coverage areas of the base stations, and a terminal device in the overlapping area can receive wireless signals from multiple base stations, so that the terminal device can be served by multiple base stations at the same time. Depending on the size of the service coverage area provided, the access network device may include a macro base station providing a macro cell, a micro base station for providing a micro cell, a micro base station for providing a micro cell, and a micro base station for providing a femto cell. In addition, access network equipment may also include various forms of relay stations, access points, remote radio units (RRUs), radio heads (RHs), remote radio heads (RRHs), etc. In systems using different wireless access technologies, the names of access network equipment may be different. For example, in the long term evolution (LTE) network, it is called evolved node B (eNB or eNodeB), in the 3G network, it is called node B (NB), in the 5G network, it may be called g node B (gNB) or NR node B (NR NB), etc.

[0074] It should be understood that in the technical solutions provided by the embodiments of the present disclosure, some repetitions may not be repeated in the introduction of the following specific embodiments, but these specific embodiments should be regarded as having been referenced to each other and can be combined with each other.

[0075] Data is generated, circulated, and consumed within communication networks, playing a significant role and considered the "new oil" of a data-driven society. 6G networks will become the foundational infrastructure for a wide range of critical information activities. With the growth of network scale, new technologies, and applications, the amount of data flowing through these networks is becoming increasingly massive and crucial. Efficient data utilization requires a comprehensive service architecture encompassing the entire data lifecycle, from generation, collection, storage, transmission, processing, analysis, exchange, and sharing. Data services are a framework based on data collection, preprocessing, distribution, publication, and analysis. They meet the requirements of data laws and regulations, balance data sharing and security, and offer data as a service. Analyzing data value discovery, regulatory requirements, technological development trends, and commercial monetization models, the demand for data services in the 6G era will be even more pressing. This demand, unlike conventional, monolithic data service architectures, requires a unified data service architecture to address these challenges.

[0076] Conventional session-oriented networks are primarily used to carry sessions—information exchange between two communicating nodes, primarily between people and machines. The establishment of a session presupposes the establishment of a communication path. Nodes along the path are solely responsible for forwarding session messages and do not process them. Forwarding is performed based on routing according to the message's destination address. With the massive amounts of data generated and consumed in the future, there is an increasing need for data-oriented networks. For example, massive amounts of data (e.g., artificial intelligence (AI) data and sensory data) need to be carried in data pipelines comprised of network-based collection, processing, transmission, storage, and analysis functions. Large amounts of data are generated and consumed by machines / algorithms. The establishment of data pipelines also relies on the establishment of communication paths in the underlying network, but each node along the data pipeline must perform appropriate processing on the message (e.g., on-path packet processing) before forwarding it to the next node and forwarding it based on the data service identifier. The differences between session-oriented routing / forwarding and data-oriented forwarding mechanisms are as follows:

[0077] Session-oriented routing / forwarding mode:

[0078] The header information used for routing remains unchanged

[0079] The data payload of the message remains unchanged

[0080] Point-to-point access

[0081] Data-oriented forwarding mechanism:

[0082] · The header information used for routing is variable

[0083] The data payload of the message is changing (data is processed along the path)

[0084] Flexible topology

[0085] Data management and processing adopt the form of pipelines. Data flows in the pipelines and completes different functions such as collection, transmission, storage, and processing between the nodes it passes through. Each network element in the communication system, such as terminals, base stations, and core networks, can participate in data services. In the data pipeline, data packets are forwarded based on data services and data pipeline identifiers. The core of the 5G user plane is to establish a protocol data unit (PDU) session, that is, to establish a session between the user terminal and the data network, and the data cannot be opened and processed at the intermediate nodes of the session. If the conventional user plane is used to carry all 6G network data, the data termination can only be done at the user plane functions (UPF), which cannot meet the distributed control of perception data, AI data, network behavior and status data. The data plane requires a new protocol stack to support flexible data service requirements.

[0086] With the reduction in computing and storage costs and the emergence of a large number of low-latency services and local applications, computing and storage, as well as the intelligent algorithms that rely on them, are trending towards deployment at the network edge, close to the data source, thus forming a data-centric network architecture. The fundamental function of mobile communication networks will also begin to shift from being information transmission pipelines to being data management and control platforms. Intrinsic perception and intelligence are two key new capabilities of 6G networks. The former uses sensor devices to perceive the network's own state, surrounding environment, and user / device behavior, generating massive amounts of data. The latter uses technologies such as AI and digital twins to perform modeling, analysis, and automated decision-making to improve network operational efficiency, enhance system performance, and provide data services for intelligent applications. Therefore, 6G networks are both producers and providers of data, providing trusted data services for intelligent applications, and consumers of data, leveraging data-driven intelligent applications to improve network performance and operational efficiency. Therefore, optimizing data governance, mining data value, and providing trusted data services pose new challenges to 6G network design.

[0087] Conventional communication networks, serving as the "pipeline" for data transmission, integrate single-point technologies for data processing, data governance, and security and privacy protection, providing specific data service capabilities for intelligent applications. However, they lack a standardized data service framework and face numerous challenges in data governance. 5G communication networks are built on sessions, with their user plane carrying session data. Because they lack the "path-associated computing" and "arbitrary topology" support required for 6G data transport, the user plane is unable to carry the new data types of 6G networks. 5G user-plane session connections enable information exchange between two communicating devices. Specifically, PDU sessions provide end-to-end user-plane connectivity between user terminals and the network. 6G data plane transmission, on the other hand, comprises functions such as data collection, preprocessing, forwarding, storage, and analysis. User plane transmission is for communication between people or between people and machines, while the data plane processes data produced and consumed by machines / algorithms. 5G user plane sessions only transmit data packets, while 6G data plane transmission networks require path-associated computing. Within the data pipeline, data is transformed and optimized to achieve the state required for data analysis and intelligent applications. In terms of data forwarding behavior, session data packets are forwarded based on the destination address; while in the data pipe, data packets are forwarded based on the data service and data pipe identifier. Data forwarding based on 5G user plane sessions belongs to the TCP / IP layer, while data forwarding on the data plane belongs to the application layer. In addition, the session-based topology is a point-to-point connection, while the 6G data plane needs to support arbitrary topology structures (such as the tree structure required for data distribution and data aggregation). If the conventional user plane is used to carry all 6G network data, the start and end of the data can only be at the two ends of the PDU session, that is, the user equipment (UE) or UPF, which cannot meet the distributed management and control of perception data, AI data, network behavior and status data. Therefore, the 6G network needs to introduce an independent data plane to build a unified, trusted, dynamic and flexible data service framework at the architectural level. While meeting data regulatory requirements, it can improve data analysis and processing efficiency, realize cross-domain and cross-manufacturer trusted data sharing, and realize the value of data through various intelligent applications.

[0088] Table 1: Comparison of data plane data load between 5G and 6G systems

[0089] Conventional data transmission methods transmit data by establishing a data channel from the UE to the UPF, but are unable to transmit data generated by access network equipment, such as AI data or perception data. To systematically address data service challenges and solve the problem that conventional mobile network user planes and data-driven architectures cannot meet the needs of new 6G services and new data, it is necessary to introduce an independent data plane for 6G networks based on 6G mobile communication network data and data services. The data plane aims to build a unified and trusted data service framework to solve the problem of data silos. While meeting the regulatory requirements of data regulations, it also provides trusted data services, enables cross-domain and cross-vendor data sharing, improves operational efficiency, and realizes the value of data. More specifically, it is expected to solve the data service scenarios where conventional session mechanisms cannot support data generated by access network equipment. Furthermore, it is expected to leverage current QoS and billing strategies while making minimal changes to communication standards.

[0090] In view of this, an embodiment of the present disclosure provides a communication method, which enables the access network device to actively initiate a session establishment process, and ultimately establish a data path between the access network device and the user plane function to carry data generated or processed by the access network device (for example, AI data, perception data, etc.). In some embodiments, the session establishment process actively initiated by the access network device can reuse the session mechanism between the conventional terminal device and the UPF without the need to redesign the session strategy, thereby reducing resource consumption. In order to make the purpose, technical solutions and advantages of the present disclosure clearer, the present disclosure will be further described in detail below with reference to the accompanying drawings. The specific operating methods, functional descriptions, etc. in the method embodiments can also be applied to device embodiments or system embodiments.

[0091] Figure 1A shows a schematic diagram of a network environment according to some embodiments of the present application. As shown in Figure 1A, system 100A may include access network equipment 110, user plane function (UPF) 120, access and mobility management function (AMF) 130, session management function (SMF) 140, data controller (DC) 150, and may further include policy control function (PCF) 160, data management core network equipment 170, application function (AF) 180 or data processing function (DPF) 190.

[0092] Although DC 150 is illustrated as being deployed on the core network (CN) side in FIG1A , this is merely exemplary. In some embodiments, DC may be deployed on the access network device side. SMF 140 and DC 150 may communicate directly or through forwarding of other devices, and this application does not specifically limit this. Compared to the conventional 5G architecture, the communication system 100A adds a data management core network device 170 for managing authentication information with the access network device. It should be understood that the term "data management core network device" is only used as an example and is not intended to be limiting, and the device may also be described using other terms. The data management core network device may also be deployed on existing devices of 5G or other communication systems as a functional module with the function of managing authentication information with the access network device. In addition, although not shown, compared to the conventional 5G architecture, the access network device 110 in the communication system 100A adds a functional module for initiating a session establishment request, which is used to request the establishment of a session between the access network device 110 and the user plane function 120.

[0093] Although only one of each device is shown in FIG1A , in implementation, any appropriate number of devices may be included depending on the scale and architecture of the network. For example, multiple UPFs 120 may be included, each data flow is sent by the same or different terminal devices, and one or more UPFs 120 are selected for the terminal devices by the SMF 140. In another example, multiple access network devices 110 may be included, each data flow is sent by the same or different access network devices, and one or more UPFs 120 are selected for the access network devices by the SMF 140.

[0094] In the example shown in FIG. 1A , a communication system 100A may include:

[0095] 1. (Radio) access network (R)AN) 110.

[0096] (R)AN can manage wireless resources, provide access services for terminal devices, and complete the forwarding of terminal device data between the terminal device and the core network. (R)AN can also be understood as a base station. For details, please refer to the previous description.

[0097] 2.UPF 120.

[0098] As the interface with the data network, the UPF performs functions such as user-plane data forwarding, session / flow-level billing and statistics, and bandwidth limitation. The UPF is responsible for almost all user-plane functions, including packet routing and forwarding, policy enforcement, traffic reporting, and quality of service (QoS) processing for user-plane data. The main functions of the UPF include: an anchor point for intra-system / inter-system mobility; an external PDU session point connected to the data network; packet routing and forwarding; partial user-plane policy rule execution and packet inspection; traffic usage reporting; an uplink classifier that supports routing service flows to the data network; a branch point that supports multi-homed PDU sessions; QoS processing for the user plane, such as packet filtering, gating, and UL / DL rate enforcement; uplink traffic verification (service data flow (SDF) to QoS flow mapping); downlink message caching, and downlink data notification triggering.

[0099] 3.AMF 130.

[0100] AMF is used to perform functions such as mobility management or access authentication / authorization. In addition, AMF is also responsible for delivering user policies between terminal devices and policy control functions. In addition, AMF can receive non-access stratum (NAS) signaling (including mobility management (MM) signaling and session management (SM) signaling) from terminal devices and related signaling from access network devices (for example, base station-level next generation (NG) 2 interface signaling that interacts with AMF), complete the user registration process, forward SM signaling, and mobility management.

[0101] 4. SMF 140.

[0102] SMF is used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of endpoints for manageable user plane functions, policy control, and charging interfaces, and downlink data notification. SMF is also used to complete processes related to the establishment, release, and update of PDU sessions.

[0103] 5. DC 150.

[0104] The DC is responsible for fine-grained, real-time data orchestration. It collaborates with the data orchestrator (DO) to achieve elasticity and programmability in the data pipeline. For details, see Figure 1B for the functional architecture of the 6G data plane.

[0105] 6. PCF 160.

[0106] PCF is responsible for user policy management, including both mobility-related policies and PDU session-related policies, such as QoS policies and billing policies.

[0107] 7. Data management core network equipment 170.

[0108] The data management core network device 170 is used to manage the authentication information (such as subscription data) of the access network device. In addition, the data management core network device 170 can also be used to manage the QoS information of the session of the access network device.

[0109] 8. Application function (AF) 180.

[0110] AF includes the following functions: interacting with the 3GPP core network to provide business or services, including: interacting with the network element function (NEF) and policy architecture interaction.

[0111] 9. Data processor function (DPF) 190.

[0112] The DPF is used to implement data processing functions, providing reliable, high-quality data for intelligent and automated decision-making algorithms. The processed data can be stored or forwarded to the next node. The UPF routes data to the DPF via the network interface.

[0113] It can be understood that the communication system 100A may also include other devices not shown. For example, the communication system 100A may also include unified data management (UDM), and UDM includes the following functions: unified data management, supporting authentication credentials processing in 3GPP authentication and key negotiation mechanism, user identity processing, access authorization, registration and mobility management, contract management and short message management, etc. The data management core network device 170 can be deployed independently in the core network or can be co-located with the UDM. The communication system 100A may also include an authentication server function network element (AUSF), and AUSF mainly includes the following functions: authentication server function, interacting with UDM to obtain registered user information, and performing authentication-related functions, such as generating intermediate keys, etc.

[0114] In the above description, the network element can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). The functional network element can be divided into one or more services, and further, there may be services that exist independently of the network function. An instance of the functional network element, an instance of a service included in the functional network element, or an instance of a service that exists independently of the network function can be referred to as a service instance.

[0115] Figure 1B illustrates a schematic diagram of a 6G mobile communication network data plane functional architecture provided for some embodiments of the present disclosure. As shown in Figure 1B, the 6G mobile communication network data plane architecture mainly includes four functional parts: data orchestrator (DO) (and data controller (DC)), data agent (DA), trusted anchor agent (TAA), and data storage function (DSF).

[0116] DO supports programmable data pipelines and implements data service request conversion (constructing data pipelines based on data service requests). DA can be built into network functions or deployed independently to perform data collection, data preprocessing, data storage, data analysis, data sharing and other data services orchestrated in the data pipeline. TAA is an independent component defined in the data plane architecture specifically for ensuring the credibility of 6G data. During the processing and use of data, it must meet the regulatory requirements of regulations such as PIPL / GDPR. If it is subjected to various security and privacy attacks from entities inside and outside the network, it will cause serious hidden dangers. Therefore, TAA plays an important role in protecting data confidentiality, integrity and reliability in 6G networks. DSF acts as a storage extension component of DA when large-scale data storage or long-term storage is required.

[0117] Based on the real-time requirements and cross-domain nature of tasks, data orchestrators are categorized into two types: DO and DC. DO is responsible for coarse-grained, non-real-time data orchestration, while DC is responsible for fine-grained, real-time orchestration tasks. Together, DO and DC achieve elasticity and programmability in the data pipeline. DO primarily performs the following functions: First, DO serves as a portal for receiving data service requests and converts them into combined requests for the data pipeline. Furthermore, DO collaborates with other network services. For example, the computing power network service orchestrates computing power, while DO orchestrates data.

[0118] Based on data service requests and the service capabilities of DA, DO can implement coarse-grained cross-domain data pipeline orchestration. At the same time, DO can have a built-in data security and privacy protection technology repository (DPTR), including technologies such as differential privacy, homomorphic encryption, secure multi-party computation, and zero-knowledge proof, providing data security and privacy protection capabilities and enabling data protection technology (DPT) to DA on demand.

[0119] In contrast, the DC can implement fine-grained DA orchestration, combining data pipelines in the local domain based on the DA's capabilities and data service requests, enabling real-time and efficient service management. Secondly, the DC receives DA capability reports and implements DA registration and deregistration functions, enabling real-time supervision of the DA by monitoring its heartbeat. Furthermore, the DC can have a built-in trusted anchor client (TAC) to initiate requests to the TAA for security mechanisms such as authentication, authorization, and access control, as well as request traceability and audit services for data access. The DC can be deployed on both the RAN and CN sides.

[0120] DA can be optionally deployed on each network function (NF), RAN, transport network (TN) node terminal, and OAM. It also supports independent deployment. By establishing a dynamic data pipeline, composed of a series of data processing units that are sequentially assembled on demand, with the output of the previous unit serving as the input for the next, DA can generate a data flow that can be output on demand from data acquisition, preprocessing, storage, and application / analysis, providing external interfaces for accessing data services.

[0121] Data collection acquires data from data sources, supporting both subscription / notification and request / response methods. The data collection request specifies the triggering method, conditions, reporting period, and data volume for data reporting. It supports the collection of user data, network data, AI data, and IoT data. It supports both streaming and batch data collection, as well as real-time and non-real-time data collection.

[0122] Data preprocessing involves a series of operations performed on collected raw data, such as cleaning, padding, smoothing, merging, normalization, and consistency checking. This process aims to improve data quality and lay the foundation for subsequent analysis. Raw data often contains dirty data, such as missing data, data noise, data redundancy, and data set imbalances.

[0123] Data privacy protection processes collected data using technologies such as k-anonymity, l-diversity, t-closeness, and ε-differential privacy. This prevents malicious attackers from directly accessing sensitive information from desensitized data, thereby safeguarding confidentiality and privacy. Data protection technology can be pre-installed in the DA or pushed on-demand by the DO, ensuring security and privacy at every level of the DA.

[0124] Data analytics are loosely coupled with DA and can be deployed separately on demand. They support various data analytics technologies, such as AI / ML, Hive, and Spark. Data analytics utilizes APIs to access DA's data collection, preprocessing, storage, and other data services. Required AI models can be pre-installed or pushed via a network service.

[0125] TAA is the agent of the 6G trusted surface on the data plane, including trusted functions such as authentication, authorization, access control, auditing, and traceability. It also provides support interfaces for trusted technologies such as blockchain to protect the confidentiality, integrity, and reliability of all data.

[0126] The data service function (DSF) is responsible for data storage, including AI model data, KPIs, logs, alarms, and other information. DSF supports unified storage of structured, unstructured, and semi-structured data; supports dynamic classification and multi-level storage of various types of files, and uses the following different data storage technologies: DSF can be a centralized database or a distributed database, such as a distributed hash table (DHT) or an interplanetary file system (IPFS). DSF supports a variety of data storage encryption technologies, such as database facade encryption, transparent data encryption (TDE), transparent file encryption (TFE), user-defined functions (UDF) encryption, and full disk encryption (FDE).

[0127] It should be understood that the communication system 100A in Figure 1A can be applied to various scenarios. For example, the application scenarios of the communication system 100A include, but are not limited to, 6G systems. The embodiments of this application are not limited to this, and it should be understood that the above-mentioned communication can comply with any appropriate communication technology and corresponding communication standards. In addition, the device names mentioned in Figure 1A are for example only and are not intended to be limiting. In future communication architectures, devices with the same functionality may be implemented. In other words, the names of the network elements shown in Figure 1A are merely names, and the names do not limit the functions of the network elements themselves. In 6G networks and other future networks, the above-mentioned network elements may also have other names, and the embodiments of this application do not specifically limit this. For example, in 6G networks, some or all of the above-mentioned network elements may continue to use 5G terminology, or may have other names, etc., which are explained here for unified explanation and will not be further elaborated below. In addition, the "network element" herein may also be referred to as a network function instance, NF, device, apparatus, or module, etc., and this application does not specifically limit it. In addition, the above-mentioned names are defined only to facilitate the distinction between different functions and should not constitute any limitation. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above-mentioned networks may continue to use the terminology in 5G, or may adopt other names, etc. The interface name between the above-mentioned network elements is only an example. The name of the interface in the specific implementation may be other names, and there is no specific limitation on this. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.

[0128] Figure 2A shows an interactive signaling diagram of a method 200A for registration of an access network device 110 according to some embodiments of the present disclosure. For illustrative purposes, Figure 2A will be described with reference to Figure 1A, and method 200A may involve the access network device 110, the AMF 130, and the data management core network device 170. It should be understood that method 200A may also include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited to this. Method 200A may be applicable to the communication system 100A of Figure 1A, and may also be applicable to other communication systems. It should be understood that the execution order of the various steps of the method shown in Figure 2A is schematic, and the steps do not have to be executed in this order. The execution order between different steps can be changed.

[0129] As shown in FIG2A , the data management core network device 170 receives 214 a first request 212. The first request 212 includes identification information of the access network device 110. The first request is used to request registration of the access network device 110 to support a session between the access network device 110 and the UPF 120. For example, the first request may be a registration request message. The data management core network device 170 stores 216 first configuration information associated with the access network device 110, the first configuration information being used to support the session between the access network device 110 and the UPF 120. For example, the first configuration information includes authentication information of the access network device 110 (e.g., subscription data of the access network device 110). Furthermore, the first configuration information may also include at least one of the following: capability information of the access network device 110, initialization policy information of the access network device 110, and QoS information for the session of the access network device 110.

[0130] In some embodiments, the data management core network device 170 may receive a first request 212 from the AMF 130. For example, the AMF 130 may receive 206 the first request 204 from the access network device 110 and configure 208 context information for the access network device 110 based on the first request 204. For example, the context information may include at least one of the following: location information of the access network device 110, permission information of the access network device 110, and IP address information of the access network device 110. The AMF 130 forwards 210 the first request 212 to the data management core network device 170. The data management core network device 170 may perform initial configuration for the access network device 110 based on the first request 212 (e.g., generate and store first configuration information) to facilitate authentication of the access network device 110 and subscription data acquisition in subsequent communications. The data management core network device 170 may then send 218 a response message 220 corresponding to the first request 212 to the AMF 130. For example, the response message 220 may be a registration response message. The AMF 130 may receive 222 a response message 220 from the data management core network device 170. The AMF 130 may send 224 rule information 226 for establishing a session to the access network device 110 and 230 a response message 232 corresponding to the first request 204 to the access network device 110. For example, the rule information may be included in a rule configuration message. For example, the rule information 226 may include at least one of the following: QoS rules for AI data communication, QoS rules for sensory data communication, and QoS rules for IoT data communication. The rule information 226 may include different QoS rules for different types of data. The access network device 110 may receive 228 the rule information 226 for establishing a session from the AMF 130 and receive 234 a response message 232 from the AMF 130. In this way, the registration process for the access network device can be completed with low signaling overhead, facilitating the session establishment process triggered by the access network device.

[0131] In some implementations, method 200A may also involve PCF 160 of FIG. 1A (not shown in FIG. 2A ). For example, data management core network device 170 may send a second request to PCF 160 based on stored first configuration information associated with access network device 110. The second request is for requesting an update of rule information associated with access network device 110. Exemplarily, the second request is a rule information update request message. Based on the second request, PCF 160 may update rule information used for session establishment, such as a policy for establishing a session between access network device 110 and UPF 120. Before sending 224 rule information 226 for session establishment to access network device 110, AMF 130 may send a third request to PCF 160. The third request is for requesting rule information associated with access network device 110. Exemplarily, the third request is a rule information request message. In response to the third request, PCF 160 may send stored rule information used for session establishment to AMF 130. The AMF 130 may receive the rule information from the PCF 160 and forward it to the access network device 110.

[0132] In some embodiments, method 200A may also involve operating, managing, and maintaining an OAM device (not shown in Figures 1A and 2A). For example, the data management core network device 170 may receive a first request from the OAM device. The first request may include identification information of the access network device 110. The first request is for requesting registration of the access network device 110 to support a dialogue between the access network device 110 and the UPF 120. For example, the first request may be a registration request message. The data management core network device 170 may perform initial configuration for the access network device 110 (e.g., generate and store first configuration information) based on the first request from the OAM device and send a fourth request to the AMF 130. The fourth request is for requesting configuration of context information for the access network device 110. For example, the fourth request may be a context configuration request message. The AMF 130 may configure the context information of the access network device 110 based on the fourth request received from the data management core network device 170 and send a response message corresponding to the fourth request to the data management core network device 170.

[0133] Similarly, data management core network device 170 may send a second request associated with access network device 110 to PCF 160 based on the stored first configuration information associated with access network device 110. PCF 160 may update the rule information for establishing a session based on the second request. After completing the context information configuration for access network device 110, AMF 130 may send a third request associated with access network device 110 to PCF 160. In response to the third request, PCF 160 sends the stored rule information for establishing a session to AMF 130. AMF 130 may receive the rule information from PCF 160 and forward it to access network device 110.

[0134] In some embodiments, a deregistration procedure for the access network device may also be performed. For example, the access network device 110 may send a fifth request to the AMF 130, requesting deregistration of the access network device 110. Exemplarily, the fifth request may be a deregistration request message. The fifth request may include identification information of the access network device 110. Based on the received fifth request, the AMF 130 may forward the fifth request, including the identification information of the access network device 110, to the data management core network device 170. Based on the received fifth request, the data management core network device 170 may release the first configuration information associated with the access network device 110 and send a response message corresponding to the received fifth request to the AMF 130. In some embodiments, the AMF 130 may also send a sixth request to the PCF 160, requesting the deletion or release of rule information for the session between the access network device 110 and the UPF 120. Exemplarily, the sixth request may be a rule information release request message or a rule information deletion request message. The PCF 160 may delete or release the rule information used to establish the session based on the sixth request, and send a response message corresponding to the sixth request to the AMF 130. The AMF 130 may send a response message corresponding to the received fifth request to the access network device 110 and release the context information of the access network device 110.

[0135] Figure 2B shows an interactive signaling diagram of a method 200B for establishing a session according to some embodiments of the present disclosure. For illustrative purposes, Figure 2B will be described with reference to Figure 1A. Method 200B may involve access network device 110, AMF 130, and SMF 140. It should be understood that method 200B may also include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0136] As shown in Figure 2B , the access network device 110 sends 240 a seventh request 242 to the AMF 130. The seventh request 242 is used to establish a session between the access network device 110 and the UPF 120 (not shown in Figure 2B ). Exemplarily, the seventh request 242 is a session establishment request message. The seventh request 242 includes identification information of the access network device 110. In some embodiments, the seventh request 242 may be sent via the N2 interface between the access network device 110 and the AMF 130.

[0137] The AMF 130 receives 244 the seventh request 242 from the access network device 110, and forwards 246 the seventh request 242 to the SMF 140. The SMF 140 receives 248 the seventh request 242 from the AMF 130, and sends 250 second configuration information 252 to the access network device 110 via the AMF 130. The access network device 110 receives 254 the second configuration information 252 for establishing a session from the SMF 140 via the AMF 130. The second configuration information 252 is used to support the session between the access network device 110 and the UPF 120. The second configuration information 252 may include configuration information for the uplink channel from the access network device 110 to the UPF 120, such as a tunnel endpoint identifier and / or a tunnel identifier from the access network device 110 to the UPF 120. For example, the second configuration information 252 may include N2 session management (SM) information (similar to the N2 SM information described in clause 4.3.2.2.1 of 3GPP TS 23.502). In some embodiments, the access network device 110 may receive the second configuration information 252 via an N2 interface.

[0138] In some embodiments, the seventh request sent by the access network device 110 to the AMF 130 may also include information indicating the device initiating the seventh request. For example, the indication may include an indication of the device type. For example, the device initiating the seventh request may be an access network device or a terminal device. If the device initiating the seventh request is a terminal device, the seventh request is used to request the establishment of a PDU session between the terminal device and the UPF 120. If the device initiating the seventh request is an access network device, the seventh request is used to request the establishment of a session between the access network device and the UPF 120. In method 200B, the device initiating the seventh request 242 is the access network device 110.

[0139] In some embodiments, the seventh request sent by the access network device 110 to the AMF 130 may also include identification information of the data service task associated with the seventh request.

[0140] In some embodiments, the seventh request 242 may further include identification information of the data service task associated with the seventh request, and the identification information may include information (e.g., type) indicating the device that initiated the seventh request. In other words, the seventh request 242 may include information related to the seventh request, such as information indicating the data service task and information indicating the device that initiated the request.

[0141] In the case where the device initiating the seventh request is an access network device, for example, in the case where the perception data is generated and sent by the access network device 110, the SMF 140 may send an eighth request associated with the access network device 110 to the data management core network device 170 (not shown in FIG2B ). The eighth request is used to request authentication information (such as subscription data) associated with the access network device. Exemplarily, the eighth request is an authentication information request message or a subscription data request message. Based on the eighth request, the data management core network device 170 may send authentication information (such as subscription data) associated with the access network device 110 to the SMF 140. Thus, the SMF 140 can complete the authentication of the access network device that initiated the seventh request 242.

[0142] In some embodiments, SMF 140 may also send third configuration information to UPF 120. The third configuration information is used to support the session between access network device 110 and UPF 120. The third configuration information may include configuration information for the downlink channel from UPF 120 to access network device 110, such as a tunnel endpoint identifier and / or tunnel identifier from UPF 120 to access network device 110. This allows a data path to be established between access network device 110 and UPF 120 without establishing a data radio bearer (DRB) between the terminal device and the access network device. When access network device 110 generates data to be transmitted, access network device 110 can send the data to be transmitted to UPF 120 via this data path.

[0143] In some embodiments, a release procedure for the session between the access network device and the UPF may also be performed. The access network device 110 may send a ninth request to the AMF 130, requesting the release of the session between the access network device and the UPF. Exemplarily, the ninth request may be a Session Release Request message. In the context of this disclosure, "release" and "delete" are used interchangeably. For example, the ninth request may request the deletion of the session between the access network device and the UPF. Exemplarily, the ninth request may be a Session Delete Request message. The ninth request may include identification information of the session between the access network device and the UPF. The AMF 130 may receive the ninth request from the access network device 110 and send it to the SMF 140. Based on the received ninth request, the SMF 140 may send a tenth request to the UPF 120, requesting the release of the session between the access network device and the UPF. Exemplarily, the tenth request may be a Session Release Request message. In some embodiments, based on the receipt of the tenth request, the UPF 120 may release the session and send a response message corresponding to the tenth request to the SMF 140. SMF 140 may send a response message corresponding to the ninth request to access network device 110, confirming the release of the session and releasing the context information associated with the session. Thus, the session between the access network device and the UPF may be released, thereby implementing lifecycle management of the session initiated by the access network device.

[0144] It can be understood that one or more embodiments of method 200A and method 200B can be implemented individually or in combination, and are all within the scope of the present disclosure. Through some embodiments of the present disclosure, it can be solved that the conventional PDU session mechanism cannot support data service scenarios where data is generated by the access network device side. Through some embodiments of the present disclosure, a session between the access network device and the UPF can be established, and the session can use the QoS policy and billing policy in the conventional PDU session. Through some embodiments of the present disclosure, it is possible to support the carrying of new types of data in the communication network, such as perception data on the base station side and AI data on the base station side.

[0145] Figure 3A illustrates an interactive signaling diagram for an example implementation of a method 300A for registration of an access network device according to some embodiments of the present disclosure. For illustrative purposes, Figure 3A will be described with reference to Figure 1A , and method 300A may involve access network device 110, AMF 130, data management core network device 170, and PCF 160. It should be understood that method 300A may include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

[0146] As shown in Figure 3A, the access network device 110 may send 302 a first request to the AMF 130 requesting registration of the access network device 110. The first request carries identification information (e.g., RAN_ID) of the access network device 110. Exemplarily, the first request is a Registration Request message. After receiving the first request, the AMF 130 may configure 304 context information corresponding to the access network device 110. The AMF 130 also forwards 306 the first request to the data management core network device 170. After receiving the first request, the data management core network device 170 may perform initial configuration 308 for the access network device 110, save the authentication information of the access network device 110, and send 312 a second request to the PCF 160 requesting that the PCF 160 update rule information associated with the access network device 110. Exemplarily, the second request is a Rule Information Update Request message. The data management core network device 170 may send 314 a response message to the AMF 130. Exemplarily, the response message may be a Registration Response message.

[0147] In some embodiments, AMF 130 may send 316 a third request to PCF 160. The third request is for requesting rule information associated with access network device 110. Exemplarily, the third request may be a rule information request message or a policy configuration request message. In response to the third request, PCF 160 may issue 318 the rule information associated with access network device 110 to access network device 110 via AMF 130. AMF 130 may send 320 a response message to access network device 110. This allows the registration process of the access network device to be implemented with low signaling overhead.

[0148] Figure 3B illustrates an interactive signaling diagram for another example implementation of a method 300A for registering an access network device according to some embodiments of the present disclosure. Figure 3B will be described with reference to Figure 1A , and method 300B may involve access network device 110, AMF 130, data management core network device 170, PCF 160, and OAM 310. It should be understood that method 300B may include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

[0149] As shown in FIG3B , the OAM 310 may send 322 a first request to the data management core network device 170 requesting registration of the access network device 110, the first request carrying identification information (e.g., RAN_ID) of the access network device 110. After receiving the first request, the data management core network device 170 may perform 324 initial configuration for the access network device 110. The data management core network device 170 may also send a fourth request to the AMF 130 requesting the AMF 130 to configure context information for the access network device 110. Exemplarily, the fourth request may be a context configuration message. The AMF 130 may configure 328 the context information corresponding to the access network device 110 and send 330 a response message corresponding to the fourth request to the data management core network device 170.

[0150] In some embodiments, the data management core network device 170 may send 332 a second request to the PCF 160, requesting the PCF 160 to update rule information associated with the access network device 110. Exemplarily, the second request is a rule information update request message. The AMF 130 may send 334 a third request to the PCF 160. The third request is for requesting rule information associated with the access network device 110. Exemplarily, the third request is a rule information request message. In response to the third request, the PCF 160 may issue 336 the rule information associated with the access network device 110 to the access network device 110 via the AMF 130. This allows the OAM-initiated registration process for access network devices to be implemented with low signaling overhead.

[0151] Figure 4 illustrates an interactive signaling diagram for an example implementation of a method 400 for deregistering an access network device according to some embodiments of the present disclosure. For illustrative purposes, Figure 4 will be described with reference to Figure 1A , and method 400 may involve access network device 110, AMF 130, data management core network device 170, and PCF 160. It should be understood that method 400 may include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

[0152] As shown in Figure 4, the access network device 110 may send 402 a fifth request to the AMF 130, where the fifth request is used to request deregistration of the access network device 110. Exemplarily, the fifth request may be a deregistration request message. The fifth request may carry identification information (e.g., RAN_ID) of the access network device 110 itself. After receiving the fifth request, the AMF 130 forwards 404 the fifth request to the data management core network device 170. After receiving the fifth request, the data management core network device 170 may search its own database and release 406 the configuration associated with the access network device 110. For example, the data management core network device 170 may delete the data corresponding to the RAN_ID and send 408 a response message corresponding to the received fifth request to the AMF 130.

[0153] In some embodiments, the access network device 110 may send 410 a sixth request to the PCF 160. The sixth request is used to request the deletion or release of rule information associated with the access network device 110. Exemplarily, the sixth request is a rule information release request message or a rule information deletion request message. Upon receiving the sixth request, the PCF 160 may release or delete the rule information associated with the access network device 110. The AMF 130 may send 412 a response message corresponding to the sixth request to the access network device 110 and release 414 the stored context information of the access network device 110. This allows the deregistration process of the access network device to be implemented with low signaling overhead.

[0154] Figure 5A shows an interactive signaling diagram of an example implementation of a method 500A for establishing a session according to some embodiments of the present disclosure. For illustrative purposes, Figure 5A will be described with reference to Figure 1A. Method 500A may involve access network device 110, AMF 130, UPF 120, SMF 140, data management core network device 170, PCF 160, DC 150, and DPF 190. It should be understood that method 500A may also include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0155] As shown in FIG5A , DC 150 may send 502 an eleventh request to access network device 110. The eleventh request is used to request the initiation of a data service. The eleventh request may carry identification information (e.g., DS_ID) of a data service task and address information of the next-hop DPF 190. Access network device 110 may send 504 a response message corresponding to the eleventh request to DC 150 and send 506 a seventh request to SMF 140. The seventh request is used to request the establishment of a session between access network device 110 and UPF 120. Exemplarily, the seventh request is a session establishment request message. In some embodiments, the seventh request may carry at least one of the following: an indication of the device initiating the seventh request (e.g., an indication of the device type, device_type); identification information (e.g., RAN_ID) of the device initiating the seventh request; and identification information (e.g., DS_ID) of the data service task.

[0156] After receiving the seventh request, SMF 140 may, based on the device_type, obtain the subscription data of the device initiating the seventh request from the data management core network device 170 or the UDM. If the device_type indicates that the device initiating the seventh request is a terminal device, SMF 140 may obtain the subscription data of the terminal device from the UDM. In method 500A, the device_type indicates that the device initiating the seventh request is an access network device. Therefore, SMF 140 may obtain the subscription data of the access network device from the data management core network device 170.

[0157] SMF 140 may send 508 an eighth request associated with access network device 110 to data management core network device 170 based on the RAN_ID. The eighth request is used to request subscription data associated with the access network device. Exemplarily, the eighth request is a subscription data request message. In response to the eighth request, data management core network device 170 may send the subscription data of access network device 110 to SMF 140, thereby enabling SMF 140 to complete authentication of the device that initiated the seventh request. SMF 140 may send 510 a twelfth request associated with access network device 110 to PCF 160. The twelfth request is used to request rule information associated with the access network device. In response to the twelfth request, PCF 160 may send the stored rule information associated with the access network device to SMF 140. Thus, SMF 140 may obtain policy rules (e.g., charging rules, QoS rules, etc.) for access network device 110. Subsequently, the SMF 140 may send 512 third configuration information for establishing a session to the UPF 120, and send 514 second configuration information for establishing a session to the access network device 110. The second and third configuration information are used to support the session between the access network device 110 and the UPF 120. The second configuration information may include configuration information for the uplink channel from the access network device 110 to the UPF 120, for example, N2 SM information (similar to the N2 SM information defined in clause 4.3.2.2.1 of TS 23.502). The third configuration information may include configuration information for the downlink channel from the UPF 120 to the access network device 110. Based on the second and third configuration information, the access network device 110 and the UPF 120 can establish a data path (similar to a conventional PDU session) without establishing a DRB between the terminal device and the access network device 110.

[0158] SMF 140 may send a response message corresponding to the seventh request to access network device 110 via AMF 130, indicating the establishment of a data path between access network device 110 and UPF 120. After the data path between access network device 110 and UPF 120 is established, access network device 110 may obtain 518 data according to the eleventh request, perform corresponding data processing, and encapsulate the IP data packet. The target IP address for data transmission is DPF 190. Access network device 110 may send 520 data to UPF 120 via the data path between access network device 110 and UPF 120, and UPF 120 then sends the data to DPF 190.

[0159] In this way, the access network device can initiate a request to establish a session between the access network device and the UPF, and the SMF selects the core network device for authentication based on the identification information in the request. As a result, data generated or processed by the access network device can be sent to the DPF via the UPF.

[0160] Figure 5B shows an interactive signaling diagram of another example implementation of method 500B for establishing a session according to some embodiments of the present disclosure. For illustrative purposes, Figure 5B will be described with reference to Figure 1A. Method 500B may involve access network device 110, AMF 130, UPF 120, SMF 140, data management core network device 170, PCF 160, DC 150, and DPF 190. The same reference numerals are used to indicate that the steps or components described in Figure 5B have the same operations as the steps or components described in Figure 5A, and their detailed descriptions will be omitted. It should be understood that method 500B may also include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0161] Compared to method 500A, in method 500B, the access network device 110 may send 506' the seventh request to the SMF 140 via the AMF 130. In some embodiments, the seventh request may carry identification information (e.g., RAN_ID) of the device initiating the seventh request and identification information DS_ID of the specialized data service task. By configuring a special identifier in the DS_ID received from the DC 150, the specialized DS_ID may include an indication of information (e.g., type) of the device initiating the seventh request. In this way, the SMF can determine that the seventh request is initiated by the access network device based on the specialized DS_ID, and obtain the subscription data of the access network device from the data management core network device 170.

[0162] SMF 140 may send 508 an eighth request associated with access network device 110 to data management core network device 170 based on the RAN_ID. The eighth request is used to request subscription data associated with the access network device. Exemplarily, the eighth request is a subscription data request message. In response to the eighth request, data management core network device 170 may send the subscription data of access network device 110 to SMF 140, thereby enabling SMF 140 to complete authentication of the device that initiated the seventh request.

[0163] Figure 5C shows an interactive signaling diagram of another example implementation of method 500C for establishing a session according to some embodiments of the present disclosure. For illustrative purposes, Figure 5C will be described with reference to Figure 1A. Method 500C may involve access network device 110, AMF 130, UPF 120, SMF 140, data management core network device 170, PCF 160, DC 150, and DPF 190. The same reference numerals are used to indicate that the steps or components described in Figure 5C have the same operations as the steps or components described in Figure 5A, and their detailed descriptions will be omitted. It should be understood that method 500C may also include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0164] Compared to method 500A, in method 500C, SMF 140 does not need to select data management core network device 170 to authenticate the access network device. Because access network device 110 is the operator's own device, SMF 140 does not need to authenticate access network device 110 again to ensure trusted data transmission. QoS charging and other policies associated with access network device 110 are stored in PCF 160. In response to receiving the seventh request, SMF 140 can directly obtain 510 the policy rules for access network device 110 from PCF 160. In this way, a session between the access network device and the UPF can be established with low signaling overhead, reducing communication latency.

[0165] Figure 6 shows an interactive signaling diagram of an example implementation of a method 600 for deleting a session according to some embodiments of the present disclosure. For illustrative purposes, Figure 6 will be described with reference to Figure 1A, and method 600 may involve access network device 110, AMF 130, UPF 120, and SMF 140. It should be understood that method 600 may also include additional blocks not shown and / or omit some of the shown blocks, and the scope of the present disclosure is not limited in this regard.

[0166] As shown in Figure 6, the access network device 110 may send 602 a ninth request to the SMF 140 via the AMF 130, requesting to release the session between the access network device 110 and the UPF 120. Exemplarily, the ninth request may be a session deletion request. The ninth request may carry identification information of the session (e.g., PDU Session ID).

[0167] After receiving the ninth request, SMF 140 may send 604 and 606 a tenth request to UPF 120 and access network device 110. The tenth request is for requesting the release of the session between UPF 120 and access network device 110. Exemplarily, the tenth request is a session release request message. In some embodiments, upon receiving the tenth request, access network device 110 and UPF 120 may release the session and send a response message corresponding to the tenth request to SMF 140. After successfully releasing the session between UPF 120 and access network device 110, SMF 140 may send 608 a response message corresponding to the ninth request to access network device 110, and then release 610 context information associated with the session. Exemplarily, the released context information may be session management context information.

[0168] FIG7 illustrates a schematic flow chart of a method 700 implemented at an access network device according to some embodiments of the present disclosure. In one possible implementation, method 700 may be implemented by access network device 110 in example communication system 100A. In other possible implementations, method 700 may also be implemented by other electronic devices independent of example communication system 100A. As an example, method 700 will be described below using the example of implementation by access network device 110 in example communication system 100A.

[0169] At 720 , the access network device 110 sends a seventh request to the access and mobility management function AMF, where the seventh request is used to request establishment of a session between the access network device and the user plane function UPF, and the seventh request includes identification information of the access network device.

[0170] At 740 , the access network device 110 receives second configuration information from the session management function SMF via the AMF, where the second configuration information includes configuration information for an uplink channel from the access network device to the UPF.

[0171] In some embodiments, the seventh request further includes at least one of the following: indication information of a device that initiates the seventh request; or identification information of a data service task associated with the seventh request.

[0172] In some embodiments, the seventh request further includes identification information of a data service task associated with the seventh request, and the identification information of the data service task includes indication information of a device that initiates the seventh request.

[0173] In some embodiments, the method may further include: sending a ninth request to the AMF, the ninth request being used to request the release of the session between the access network device and the UPF, the ninth request including identification information of the session; receiving a tenth request from the SMF via the AMF, the tenth request being used to request the release of the session between the access network device and the UPF; and receiving a response message corresponding to the ninth request from the SMF via the AMF.

[0174] In some embodiments, the method may further include: sending a first request to the AMF, the first request being used to request registration of the access network device, the first request including identification information of the access network device; receiving rule information for establishing a session from the AMF; and receiving a response message corresponding to the first request from the AMF.

[0175] In some embodiments, the method may further include: sending a fifth request to the AMF, the fifth request being used to request execution of deregistration of the access network device, the fifth request including identification information of the access network device; and receiving a response message corresponding to the fifth request from the AMF.

[0176] In some embodiments, the seventh request is sent over the N2 interface, and the configuration information is received over the N2 interface.

[0177] FIG8 is a schematic flow chart of another method 800 implemented at an access network device according to some embodiments of the present disclosure. In one possible implementation, method 800 may be implemented by access network device 110 in example communication system 100A. In other possible implementations, method 800 may also be implemented by other electronic devices independent of example communication system 100A. As an example, method 800 will be described below using the example of being implemented by access network device 110 in example communication system 100A.

[0178] At 820, the access network device 110 sends a first request to the AMF, where the first request is used to request registration of the access network device, and the first request includes identification information of the access network device.

[0179] At 840 , the access network device 110 receives rule information for establishing a session from the AMF.

[0180] At 860 , the access network device 110 receives a response message corresponding to the first request from the AMF.

[0181] In some embodiments, the method may further include: sending a fifth request to the AMF, the fifth request being used to request execution of deregistration of the access network device, the fifth request including identification information of the access network device; and receiving a response message corresponding to the fifth request from the AMF.

[0182] Figure 9 shows a schematic flow chart of a method 900 implemented at an AMF according to some embodiments of the present disclosure. In one possible implementation, method 900 may be implemented by AMF 130 in example communication system 100A. In other possible implementations, method 900 may also be implemented by other electronic devices independent of example communication system 100A. As an example, method 900 will be described below using implementation by AMF 130 in example communication system 100A as an example.

[0183] At 920, the AMF 130 receives a seventh request from the access network device, where the seventh request is used to request establishment of a session between the access network device and the user plane function UPF, and the seventh request includes identification information of the access network device.

[0184] At 940 , the AMF 130 sends a seventh request to the session management function SMF.

[0185] In some embodiments, the seventh request further includes at least one of the following: indication information of a device that initiates the seventh request; or identification information of a data service task associated with the seventh request.

[0186] In some embodiments, the seventh request further includes identification information of a data service task associated with the seventh request, and the identification information of the data service task includes indication information of a device that initiates the seventh request.

[0187] In some embodiments, the method may also include: receiving a first request from an access network device, the first request being used to request registration of the access network device, the first request including identification information of the access network device; configuring context information of the access network device based on the first request; sending a first request to a core network device, the core network device being used to manage subscription data associated with the access network device; receiving a response message corresponding to the first request from the core network device; sending a third request associated with the access network device to a policy control function PCF, the third request being used to request rule information associated with the access network device; receiving rule information for establishing a session from the PCF; sending rule information for establishing a session to the access network device; and sending a response message corresponding to the first request to the access network device.

[0188] In some embodiments, the method may also include: receiving a fourth request associated with the access network device from the core network device, the fourth request being used to request configuration of context information for the access network device, and the core network device being used to manage subscription data associated with the access network device; configuring the context information of the access network device based on the fourth request; sending a response message corresponding to the fourth request to the core network device; sending a third request associated with the access network device to the PCF, the third request being used to request rule information associated with the access network device; receiving rule information for establishing a session from the PCF; and sending rule information for establishing a session to the access network device.

[0189] In some embodiments, the method may also include: receiving a fifth request from the access network device, the fifth request being used to request execution of deregistration of the access network device, the fifth request including identification information of the access network device; sending a fifth request to the core network device, the core network device being used to manage subscription data associated with the access network device; receiving a response message corresponding to the fifth request from the core network device; sending a sixth request associated with the access network device to the PCF, the sixth request being used to request deletion or release of rule information for a session between the access network device and the UPF; receiving a response message corresponding to the sixth request from the PCF; sending a response message corresponding to the fifth request to the access network device; and releasing context information of the access network device.

[0190] In some embodiments, the method may further include: receiving a ninth request from the access network device, the ninth request being used to request the release of the session between the access network device and the UPF, the ninth request including identification information of the session; and sending the ninth request to the SMF.

[0191] FIG10 is a schematic flow chart of a method 1000 implemented at an SMF according to some embodiments of the present disclosure. In one possible implementation, method 1000 may be implemented by SMF 140 in example communication system 100A. In other possible implementations, method 1000 may also be implemented by other electronic devices independent of example communication system 100A. As an example, method 1000 will be described below using the example of being implemented by SMF 140 in example communication system 100A.

[0192] At 1020, the SMF 140 receives a seventh request from the access and mobility management function AMF, where the seventh request is used to request establishment of a session between the access network device and the user plane function UPF, and the seventh request includes identification information of the access network device.

[0193] At 1040, SMF 140 sends second configuration information to the access network device, where the second configuration information includes configuration information for an uplink channel from the access network device to the UPF.

[0194] In some embodiments, the seventh request further includes at least one of the following: indication information of a device that initiates the seventh request; or identification information of a data service task associated with the seventh request.

[0195] In some embodiments, the seventh request further includes identification information of a data service task associated with the seventh request, and the identification information of the data service task includes indication information of a device that initiates the seventh request.

[0196] In some embodiments, the method may also include: based on determining that the type of the device is an access network device type, sending an eighth request associated with the access network device to the core network device, the eighth request being used to request subscription data associated with the access network device, and the core network device being used to manage subscription data associated with the access network device; and receiving subscription data from the core network device.

[0197] In some embodiments, the method may further include: receiving a ninth request from the AMF, the ninth request being used to request the release of the session between the access network device and the UPF, the ninth request including identification information of the session; sending a tenth request to the access network device and the UPF, the tenth request being used to request the release of the session between the access network device and the UPF; sending a response message or confirmation message corresponding to the ninth request to the access network device; and releasing context information associated with the session.

[0198] Figure 11 illustrates a schematic flow chart of a method 1100 implemented at a data management core network device according to some embodiments of the present disclosure. In one possible implementation, method 1100 may be implemented by data management core network device 170 in example communication system 100A. In other possible implementations, method 1100 may also be implemented by other electronic devices independent of example communication system 100A. As an example, method 1100 will be described below using implementation by data management core network device 170 in example communication system 100A as an example.

[0199] At 1120 , the data management core network device 170 receives a first request, where the first request is used to request registration of the access network device, and the first request includes identification information of the access network device.

[0200] At 1140 , the data management core network device 170 stores context information associated with the access network device, where the context information is used to support a session between the access network device and a user plane function (UPF).

[0201] In some embodiments, the first request is received from an operation, administration and maintenance OAM device, and the method may further include: sending a fourth request associated with the access network device to the AMF, the fourth request being used to request configuration of context information for the access network device; receiving a response message corresponding to the fourth request from the AMF; and sending a second request associated with the access network device to the PCF, the second request being used to request an update of rule information associated with the access network device.

[0202] In some embodiments, the method may further include: receiving a fifth request from the AMF, the fifth request being used to request execution of deregistration of the access network device, the fifth request including identification information of the access network device; releasing context information associated with the access network device; and sending a response message corresponding to the fifth request to the AMF.

[0203] In some embodiments, the method may further include: receiving an eighth request associated with the access network device from the session management function SMF, the eighth request being used to request subscription data associated with the access network device; and sending the subscription data associated with the access network device to the SMF.

[0204] Figure 12 is a schematic diagram of the structure of possible communication devices (also referred to as communication equipment) provided in an embodiment of the present disclosure. These communication devices can implement the functions of the terminal device or network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiment of the present disclosure, the communication device can be the access network device 110, AMF 130, SMF 140, or data management core network device 170 in Figure 1A.

[0205] As shown in Figure 12, a communication device 1200 includes a processing unit 1210, a receiving unit 1220, and a sending unit 1230. The communication device can be used to implement the functions of registering or deregistering an access network device, establishing a session, or deleting a session in the method embodiments shown in any of Figures 1 to 11. In some embodiments, the processing unit can be a processor, the sending unit can be a transmitter, and the receiving unit can be a receiver.

[0206] FIG13 is a simplified block diagram of a possible communication device (also referred to as a communication apparatus) provided in accordance with an embodiment of the present disclosure. As shown in FIG13 , the communication device 1300 includes a processor 1310 and an interface circuit 1320. The processor 1310 and the interface circuit 1320 are coupled to each other. It will be appreciated that the interface circuit 1320 may be a transceiver or an input / output interface. Optionally, the communication device 1300 may further include a memory 1330 for storing instructions executed by the processor 1310 or for storing input data required by the processor 1310 to execute instructions or for storing data generated after the processor 1310 executes instructions.

[0207] When the communication device 1300 is used to implement the method in the above method embodiment, the processor 1310 is used to execute the functions of the above processing unit 1210, and the interface circuit 1320 is used to execute the functions of the above receiving unit 1220 and the sending unit 1230.

[0208] It is understood that the processor in the embodiments of the present disclosure may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0209] The embodiments of the present disclosure provide a communication system. The communication system may include the communication device involved in the embodiment shown in Figure 12 above, such as the access network device 110, AMF 130, SMF 140, or data management core network device 170 of Figure 1A or its module (such as a chip). Optionally, the access network device 110, AMF 130, SMF 140, or data management core network device 170 of Figure 1A or its module (such as a chip) in the communication system may execute any of the communication methods shown in Figures 1 to 11.

[0210] The present disclosure also provides a circuit that can be coupled to a memory and can be used to execute a process related to the access network device 110, AMF 130, SMF 140, or data management core network device 170 or its module (such as a chip) in any of the above method embodiments. The chip system may include the chip and other components such as a memory or a transceiver.

[0211] It should be understood that the processor mentioned in the embodiments of the present disclosure may be a CPU, or may be other general-purpose processors, 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, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0212] It should also be understood that the memory mentioned in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0213] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated into the processor.

[0214] It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

[0215] It should be understood that in the various embodiments of the present disclosure, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present disclosure.

[0216] Those skilled in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0217] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0218] In the several embodiments provided herein, it should be understood that the disclosed communication methods and devices can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the module division is merely a logical functional division. In actual implementation, other division methods may be used, such as combining or integrating multiple modules or components into another system, or omitting or not implementing certain features. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interface. Indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0219] The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network elements. Some or all of these elements may be selected to achieve the purpose of this embodiment according to actual needs.

[0220] In addition, each functional module in each embodiment of the present disclosure may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0221] If this function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure, or the part that makes the contribution, or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method of each embodiment of the present disclosure. The aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, mobile hard disk, or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0222] As used herein, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. can refer to different or the same objects and are only used to distinguish the objects referred to, and do not imply a specific spatial order, temporal order, order of importance, etc. of the objects referred to. In some embodiments, values, processes, selected items, determined items, devices, means, components, assemblies, etc. are referred to as "best", "lowest", "highest", "minimum", "maximum", etc. It should be understood that such descriptions are intended to indicate that a selection can be made from a number of available functional options, and that such a selection need not be better, lower, higher, smaller, larger, or otherwise preferred than other options in other aspects or all aspects. As used herein, the term "determine" can encompass a variety of actions. For example, "determine" can include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or another data structure), ascertaining, etc. Furthermore, "determining" may include receiving (eg, receiving information), accessing (eg, accessing data in a memory), etc. Furthermore, "determining" may include resolving, selecting, choosing, establishing, etc.

[0223] The above is only a specific embodiment of the present application, but the scope of protection of the embodiments of the present application is not limited thereto. Any person skilled in the art can easily conceive of changes or substitutions within the technical scope disclosed in the embodiments of the present application, and all such changes or substitutions should be included in the scope of protection of the embodiments of the present application. Therefore, the scope of protection of the embodiments of the present application should be based on the scope of protection of the claims.

Claims

1. A method for network device session management, comprising: Sending a first request to an access and mobility management function AMF, where the first request is used to request establishment of a session between an access network device and a user plane function UPF, and the first request includes identification information of the access network device; as well as The first configuration information is received from the session management function SMF via the AMF, wherein the first configuration information includes configuration information for the uplink channel from the access network device to the UPF.

2. The method according to claim 1, wherein the first request further comprises at least one of the following: Indication information of the device that initiated the first request; or Identification information of the data service task associated with the first request. 3 . The method according to claim 1 , wherein the first request further comprises identification information of a data service task associated with the first request, the identification information of the data service task comprising indication information of a device that initiates the first request.

4. The method according to any one of claims 1 to 3, wherein the method further comprises: Sending a second request to the AMF, where the second request is used to request to release the session between the access network device and the UPF, and the second request includes identification information of the session; A response message corresponding to the second request is received from the SMF via the AMF.

5. The method according to any one of claims 1 to 4, wherein the method further comprises: Sending a third request to the AMF, where the third request is used to request registration of the access network device, and the third request includes identification information of the access network device; receiving, from the AMF, rule information for establishing the session; as well as receiving a response message corresponding to the third request from the AMF.

6. The method according to any one of claims 1 to 5, wherein the method further comprises: Sending a fourth request to the AMF, where the fourth request is used to request execution of deregistration of the access network device, and the deregistration request includes identification information of the access network device; as well as receiving a response message corresponding to the fourth request from the AMF.

7. The method according to any one of claims 1 to 6, wherein the first request is sent through an N2 interface, and the first configuration information is received through the N2 interface.

8. A method for network device session management, comprising: receiving a first request from an access network device, where the first request is used to request to establish a session between the access network device and a user plane function UPF, and the first request includes identification information of the access network device; as well as The first request is sent to a session management function SMF.

9. The method of claim 8, wherein the first request further comprises at least one of the following: Indication information of the device that initiated the first request; or Identification information of the data service task associated with the first request.

10. The method according to claim 8, wherein the first request further comprises identification information of a data service task associated with the first request, the identification information of the data service task comprising indication information of a device that initiates the first request.

11. The method according to any one of claims 8 to 10, wherein the method further comprises: receiving a third request from the access network device, the third request being used to request to perform registration of the access network device, the third request including the identification information of the access network device; configuring context information of the access network device based on the third request; Sending the third request to a core network device, where the core network device is used to manage subscription data associated with the access network device; receiving a response message corresponding to the third request from the core network device; Sending a fifth request associated with the access network device to a policy control function PCF, wherein the fifth request is used to request rule information associated with the access network device; receiving the rule information for establishing the session from the PCF; Sending the rule information for establishing the session to the access network device; as well as Sending a response message corresponding to the third request to the access network device.

12. The method according to any one of claims 8 to 10, wherein the method further comprises: receiving, from a core network device, a sixth request associated with the access network device, the sixth request being used to request configuration of context information for the access network device, the core network device being used to manage subscription data associated with the access network device; configuring the context information of the access network device based on the sixth request; Sending a response message corresponding to the sixth request to the core network device; Sending a fifth request associated with the access network device to the PCF, wherein the fifth request is used to request rule information associated with the access network device; receiving the rule information for establishing the session from the PCF; as well as The rule information for establishing the session is sent to the access network device.

13. The method according to any one of claims 8 to 12, wherein the method further comprises: receiving a fourth request from the access network device, the fourth request being used to request execution of deregistration of the access network device, the fourth request including the identification information of the access network device; Sending the fourth request to a core network device, where the core network device is used to manage subscription data associated with the access network device; receiving a response message corresponding to the fourth request from the core network device; Sending a seventh request associated with the access network device to the PCF, the sixth request being used to request release of rule information for the session between the access network device and the UPF; receiving, from the PCF, a response message corresponding to the seventh request; Sending a response message corresponding to the fourth request to the access network device; as well as The context information of the access network device is released.

14. The method according to any one of claims 8 to 13, wherein the method further comprises: receiving a second request from the access network device, wherein the second request includes identification information of the session; as well as Send the second request to the SMF.

15. A method for managing a network device session, comprising: receiving a first request from an access and mobility management function AMF, the first request being used to request establishment of a session between an access network device and a user plane function UPF, the first request including identification information of the access network device; as well as Send first configuration information to the access network device via the AMF, where the first configuration information includes configuration information for an uplink channel from the access network device to the UPF.

16. The method of claim 15, wherein the first request further comprises at least one of the following: Indication information of the device that initiated the first request; or Identification information of the data service task associated with the first request. 17 . The method according to claim 15 , wherein the first request further comprises identification information of a data service task associated with the first request, the identification information of the data service task comprising indication information of a device that initiates the first request.

18. The method according to claim 16 or 17, wherein the method further comprises: Based on determining that the indication information of the device is access network device indication information, sending an eighth request associated with the access network device to a core network device, the eighth request being used to request subscription data associated with the access network device, and the core network device being used to manage the subscription data associated with the access network device; as well as The subscription data is received from the core network device.

19. The method according to any one of claims 15 to 18, wherein the method further comprises: receiving a second request from the AMF, where the second request is used to request to release the session between the access network device and the UPF, and the second request includes identification information of the session; Sending, via the AMF, an indication of releasing the session to the access network device and to the UPF; Sending a response message corresponding to the second request to the access network device via the AMF; as well as The context information associated with the session is released.

20. A method for network device session management, comprising: receiving a third request, the third request being used to request registration of an access network device, the third request including identification information of the access network device; as well as Context information associated with the access network device is stored, where the context information is used to support a session between the access network device and a user plane function UPF.

21. The method of claim 20, wherein the third request is received from an operations, administration, and maintenance (OAM) device, the method further comprising: Sending a sixth request associated with the access network device to the AMF, where the sixth request is used to request configuration of context information for the access network device; receiving, from the AMF, a response message corresponding to the sixth request; as well as A ninth request associated with the access network device is sent to the PCF, where the ninth request is used to request an update of rule information associated with the access network device.

22. The method according to claim 20 or 21, wherein the method further comprises: receiving a fourth request from the AMF, the fourth request including the identification information of the access network device; Releasing context information associated with the access network device; as well as Send a response message corresponding to the fourth request to the AMF.

23. The method according to any one of claims 20 to 22, wherein the method further comprises: receiving, from a session management function SMF, an eighth request associated with the access network device, the eighth request being used to request subscription data associated with the access network device; as well as Send the subscription data associated with the access network device to the SMF.

24. A communication device, comprising: processor; as well as A memory storing instructions, wherein when the instructions are executed by the processor, the communication device executes the method according to any one of claims 1 to 7.

25. A communication device, comprising: processor; as well as A memory storing instructions, wherein when the instructions are executed by the processor, the communication device executes the method according to any one of claims 8 to 14.

26. A communication device, comprising: processor; as well as A memory storing instructions, wherein when the instructions are executed by the processor, the communication device executes the method according to any one of claims 15 to 19.

27. A communication device, comprising: processor; as well as A memory storing instructions, wherein when the instructions are executed by the processor, the communication device performs the method according to any one of claims 20 to 23.

28. A communication system comprising: The communication device according to claim 24, the communication device according to claim 25, the communication device according to claim 26, and the communication device according to claim 27.

29. A computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the instructions are executed by a device, the device performs the method according to any one of claims 1 to 7.

30. A computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the instructions are executed by a device, the device performs the method according to any one of claims 8 to 14.

31. A computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the instructions are executed by a device, the device performs the method according to any one of claims 15 to 19.

32. A computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when executed by a device, cause the device to perform the method according to any one of claims 20 to 23.

33. A computer program product, comprising instructions, which, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 7.

34. A computer program product comprising instructions which, when executed on a computer, cause the computer to perform the method according to any one of claims 8 to 14.

35. A computer program product comprising instructions which, when executed on a computer, cause the computer to perform the method according to any one of claims 15 to 19.

36. A computer program product comprising instructions which, when executed on a computer, cause the computer to perform the method according to any one of claims 20 to 23.

Images